Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
We have a customer that has very bursty traffic. Having a maximum of 100 threads for flushing the disruptor queues ends up creating a lot of CPU load when these bursts happen. They really want to be able to set the maximum number of threads lower to reduce the CPU utilization and are OK with the increased latency that comes with it.
Attachments
Issue Links
- links to