Because the queue processes all tasks at once, the ThrottleComputationQueueTaskDispatcher's current implementation of checking what is currently executing misses out on what is currently being scheduled and so as a result you can get more than the limit of 5 processing from scheduled to executing at the same time and then the CPU resources are starved serving potentially 100's of concurrent indexing jobs.