Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-24457

VERY poor performance with large test history when viewing results.

      It takes about 20 sec to display any part of the test report when the json file is big enough and there are lots of previous builds.

          [JENKINS-24457] VERY poor performance with large test history when viewing results.

          Anatoly Bubenkov created issue -

          James Nord added a comment -

          Can you be specific on exactly what is slow?

          Parsing the results in the build?
          Displaying a feature in the ui?
          Something else.

          If it us the display in the ui then 90% chance your jvm heap is too small. Try increasing it and report back.

          If not please attach a json file that is slow.

          We observe instant display in a correctly configured system with what i would consider as large features.

          James Nord added a comment - Can you be specific on exactly what is slow? Parsing the results in the build? Displaying a feature in the ui? Something else. If it us the display in the ui then 90% chance your jvm heap is too small. Try increasing it and report back. If not please attach a json file that is slow. We observe instant display in a correctly configured system with what i would consider as large features.
          Anatoly Bubenkov made changes -
          Attachment New: FUNCTIONAL-results.json [ 26708 ]

          Displaying in the ui is the thing which is super slow, parsing, looks OK.
          I've attached the file. JVM heap size cannot be easily increased because it's already quite optimal...

          Anatoly Bubenkov added a comment - Displaying in the ui is the thing which is super slow, parsing, looks OK. I've attached the file. JVM heap size cannot be easily increased because it's already quite optimal...

          James Nord added a comment - - edited

          That file is small.
          I really urgue you too look at jvmstat when trying to display as I bet you will see lots of gc activity.

          The plugin loads previous results, but Jenkins stores these in a weak reference and so are the first things to go. So when memory is low loading them up will cause other results to be gced so Jenkins ends up fighting the GC.

          I will run them through my system but I am expecting instant display.

          James Nord added a comment - - edited That file is small. I really urgue you too look at jvmstat when trying to display as I bet you will see lots of gc activity. The plugin loads previous results, but Jenkins stores these in a weak reference and so are the first things to go. So when memory is low loading them up will cause other results to be gced so Jenkins ends up fighting the GC. I will run them through my system but I am expecting instant display.

          James Nord added a comment -

          If I set a small enough heap I can make a machine spin forever trying to display the results.
          The same is true to some extent for junit results - but to a lesser degree as the files it loads are smaller.

          James Nord added a comment - If I set a small enough heap I can make a machine spin forever trying to display the results. The same is true to some extent for junit results - but to a lesser degree as the files it loads are smaller.

          ah ok!
          then which size would you recommend in our situation?

          http://pastebin.com/pxANWJBE

          Anatoly Bubenkov added a comment - ah ok! then which size would you recommend in our situation? http://pastebin.com/pxANWJBE

          Anatoly Bubenkov added a comment - - edited

          Anatoly Bubenkov added a comment - - edited and memory http://pastebin.com/1cDeRysb

          James Nord added a comment -

          this file has instant display on my system.

          I suggest you buy more RAM or upgrade the VM - 4GB is on the small side for a server and you only have 200 free.
          I would only suggest tuning so you have more young space at the expence of the old if you can not add more ram.
          99% usage of the eden is not so good.

          as an asside - the results are missing timing information - you may want to file a defect against the cucumber-xxx version you are using.

          James Nord added a comment - this file has instant display on my system. I suggest you buy more RAM or upgrade the VM - 4GB is on the small side for a server and you only have 200 free. I would only suggest tuning so you have more young space at the expence of the old if you can not add more ram. 99% usage of the eden is not so good. as an asside - the results are missing timing information - you may want to file a defect against the cucumber-xxx version you are using.

          James Nord added a comment -

          as per above - not enough free memory causing GC churn on sysytem

          James Nord added a comment - as per above - not enough free memory causing GC churn on sysytem
          James Nord made changes -
          Resolution New: Not A Defect [ 7 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

            Unassigned Unassigned
            bubenkoff Anatoly Bubenkov
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: