Uploaded image for project: 'Decision Automation Group'
  1. Decision Automation Group
  2. DAG-957

Add visualization of ops/sec throughput on Longevity Tests task page

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Gone away
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Perf Tools
    • Labels:
      None

      Description

      In the 50/50 suite there are huge dips in throughput over time. For example on this task we see the following:

      10 sec: 320718 operations; 32030.16 current ops/sec; [UPDATE AverageLatency(us)=2071.94] [READ AverageLatency(us)=1776.63] 
      20 sec: 720059 operations; 39930.11 current ops/sec; [UPDATE AverageLatency(us)=1689.89] [READ AverageLatency(us)=1507.28] 
      30 sec: 1067230 operations; 34717.1 current ops/sec; [UPDATE AverageLatency(us)=1893.37] [READ AverageLatency(us)=1785.66] 
      40 sec: 1159908 operations; 9266.87 current ops/sec; [UPDATE AverageLatency(us)=7105.21] [READ AverageLatency(us)=6606.64] 
      50 sec: 1176859 operations; 1695.1 current ops/sec; [UPDATE AverageLatency(us)=36490.75] [READ AverageLatency(us)=38854.54] 
      60 sec: 1186237 operations; 937.71 current ops/sec; [UPDATE AverageLatency(us)=66998.58] [READ AverageLatency(us)=67860.94] 
      70 sec: 1195197 operations; 896 current ops/sec; [UPDATE AverageLatency(us)=72223.09] [READ AverageLatency(us)=71878.21] 
      80 sec: 1202846 operations; 764.9 current ops/sec; [UPDATE AverageLatency(us)=81654.81] [READ AverageLatency(us)=84713.76] 
      90 sec: 1312222 operations; 10936.51 current ops/sec; [UPDATE AverageLatency(us)=5948.9] [READ AverageLatency(us)=5962.97] 
      100 sec: 1629937 operations; 31771.5 current ops/sec; [UPDATE AverageLatency(us)=1995.34] [READ AverageLatency(us)=1961.7]
      

      Presumably the load phase has the same problem. Goal here is to get a visual representation of the throughput over time so we can watch for this spikiness. Perf team will be responsible for adding automated catching of this spikiness.

        Attachments

          Activity

            People

            Assignee:
            backlog-server-evg Backlog - Evergreen Team
            Reporter:
            ian.whalen Ian Whalen
            Participants:
            Last commenter:
            Iryna Zhuravlova Iryna Zhuravlova
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Days since reply:
              1 year, 43 weeks, 2 days ago
              Date of 1st Reply: