We have some jobs with a large number of artifacts (~4000 files in ~1200 directories per build). Displaying the job page for one of these jobs takes 30 seconds or more. These jobs do not use the NeoLoad plugin at all. Deinstalling the plugin makes the job page display in under 1 second.

The reason is that the plugin's action are executed for every job, whether it uses the plugin or not. The action scans all artifacts of all builds of the job looking for the (one) NeoLoad results file (cf. findXMLResultsFile).

The plugin should run the action only if the job actually uses the plugin. If that's not possible, I suggest an approach similar to what the JUnit plugin does: look for the test result file in post-build and persist that file with a fixed name (but not as an artifact).