-
Improvement
-
Resolution: Done
-
Medium
-
None
-
None
-
None
Downstream project has encountered high cpu usage linked to the lmax disruptor, which was traced to it busy looping even when there were no events produced. We might be able to replace this with QueuedNotificationManager without any issues.