Uploaded image for project: 'mdsal'
  1. mdsal
  2. MDSAL-546

Replace lmax disruptor with QueuedNotificationManager

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Done
    • Icon: Medium Medium
    • 7.0.0
    • 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.

            tcere Tomas Cere
            tcere Tomas Cere
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: