sonus21 / rqueue / 843

90%

master: 84%

Pull #87

circleci

Old
----
Core thread pool size = queueCount
Max thread pool size =  3 * queueCount
If number of queue < 10, its good but as soon as we increase the number of queues, thread pool size and similarly number of jobs those are fighting for CPU.
Consider a case with 100 queues, it will enqueue 300 jobs at some point of time, that's insane for one machine.  100 jobs are always enqueued for polling messages.

New
----
Core Thread Pool size = min(queueCount, 5 * CpuCount, 10)
Max Pool size = queueCount + min(queueCount*2, 10 * CpuCount, 50)

So for 100 queues, we'll have 150 executing job at any point of time, in that 100 jobs would be polling messages and 50 would be executing workers task.

Still if we look at number of jobs are insane, there are 100 jobs just to pull message from queue, the correct strategy would be put queues in group using priorityGroup and also consider not running more than 30 listeners on one box. Listeners should be distributed using active field.

35 of 35 new or added lines in 3 files covered. (100.0%)

4764 of 5300 relevant lines covered (89.89%)

0.9 hits per line