The ShardingTaskExecutor's reactor thread is a potential availability bottleneck when it falls behind, because all requests in the mongos must schedule tasks on it in order to service their requests to shards. Under overload in the find_max_time_ms workload, logging is taking up 7% of CPU time on the thread-- we could consider pushing these logs to a separate thread to offload the expensive blocking work from one of our most sensitive threads.