In find_time_max_ms, the mongos sharding task executor reactor thread spends a significant amount of time on a mutex in ShardingTaskExecutorPoolController::updateHost – this function appears to be relatively lightweight, and so its unclear why there is so much contention here. We should do an investigation of this codepath in order to understand the contention under overload, as it appears to be a significant bottleneck.