| fwiw, our workplace was having similar out-of-memory issues with our Jenkins server recently. I tracked it down to this "test-results-analyzer" plugin also, as it was chewing up 2.9GB with just string-data. Initially, I wrongly assumed that this plugin was responsible for the "Test Result" page of the interface, hence assumed this was a plugin that we needed. 
However, I finally realised that this plugin is responsible for entirely different output. It provides a link called "Test Results Analyzer" which collates a large table of all your test results across all your builds. More info at this link. 
So I now understood why it was chewing up so much string data, some of our projects have build histories consisting of up to 2000 builds, with hundreds of tests in them. So this would have resulted in an absolutely enormous table!  So with that understanding under my belt, I felt safe to delete this plugin, as our team has no need for it. Just wanted to share this experience, in-case others are experiencing this same confusion between these two things. |
