Unnecessary idle time between timer trigger processing in history syncer

XMLWordPrintable

    • Type: Problem report
    • Resolution: Fixed
    • Priority: Trivial
    • 4.0.0beta2, 4.0 (plan)
    • Affects Version/s: 4.0.0beta1
    • Component/s: Server (S)
    • None
    • Sprint 42, Sprint 43, Sprint 44, Sprint 45
    • 0.5

      When there are no history data to process (history cache is empty), but there are a 500+ timer triggers in queue, history syncer will process 500 timer triggers and enter idle state for 1 sec instead of immediately processsing the next batch of timer triggers.

            Assignee:
            Andris Zeila
            Reporter:
            Andris Zeila
            Team A
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: