Uploaded image for project: 'OpenNMS'
  1. OpenNMS
  2. NMS-9846

Improve event processing rate in alarmd (for databases with high latency)

    XMLWordPrintable

    Details

    • Sprint:
      Horizon - Feb 1st 2018, Horizon - Feb 7th 2018

      Description

      Alarmd is currently single threaded. When processing events with alarm data, alarmd must at least do one database query (usually multiple) to create or update the alarm. If the minimal latency for a single query is 5ms, this means that we could at most process 200 events per second.

      In order to work around, we should be able to handle events over multiple threads while ensuring that triggers and clears associated to a particular alarm continue to be processed in order.

        Attachments

          Activity

            People

            • Assignee:
              j-white Jesse White
              Reporter:
              j-white Jesse White
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: