Stop showing all of the performance plots - #96
Conversation
There are now over 1000 PNG plots being generated during the nightly performance jobs. This makes the build page WAY too big and take really long to load. Even after it does, finding the plot you're interested in is almost impossible given that there are no text titles to search for (the titles are embedded in the images). I think we should just disable the image gallery plugin. We can keep the plots as archived file artifacts so that they can be linked to from the build-over-build plots.
Would it make sense to at least show some selected plots? |
@ahcorde, do you have any thoughts about this? Is there some subset of of the current results you believe might be interesting to display on the build page? The patterns appear to use "ant syntax", but that doesn't seem to buy us much here. I don't see a way to do "exclude" filtering on the matches. |
|
These plots will be always available clicking in the plots that generate the Jenkins plot plugin. All these plots ae unsorted, it's difficult to find what you are looking for or understand what is going on. +1 to remove it. Maybe you can show only "latency" but I don't have a strong opinion on that. |
|
@cottsay What is the status on this? |
libfranka needs at least GCC 5 to compile.
There are now over 1000 PNG plots being generated during the nightly performance jobs. This makes the build page WAY too big and take really long to load. Even after it does, finding the plot you're interested in is almost impossible given that there are no text titles to search for (the titles are embedded in the images).
I think we should just disable the image gallery plugin. We can keep the plots as archived file artifacts so that they can be linked to from the build-over-build plots.
Results in the following diff:
Details