Jenkins Warnings Plugin Slow?

[Trinition]

We're using the Warnings Plugin in our CI build, and doing some time-stamp logging in our build, I've found that 1 miunte of our 13 minute build is spent here:

11:13.1 00:10.6 [WARNINGS] Parsing warnings in console log with parser MSBuild Custom

11:23.8 01:10.8 [WARNINGS] Computing warning deltas based on reference build #515

12:34.5 00:00.0 [TASKS] Scanning folder 'C:\Workspace\MyProject' for files matching the pattern '**/*.cs,**/*.xaml' - excludes: 

The first column is a relative timestamp within the build (thanks to Timestamper plugin).  The second column is the time until the next timestamp.  So the time between "Parsing warnings"... until "Computing warning deltas" was 10 seconds.  But then the time from "Computing warning deltas" until the task scanning starts was over 1 minute!

I don't know exactly what the warning delta calculation involves, but it appears to be quite intensive!

Does anyone have insight to why this might be slow?

FWIW, out project has ~50 warnings out of 1M+ lines of code (though the warnings are extracted from the build's console output, not the source lines).

[Trinition]

I think this is the code that actually calculates the deltas (correct me if I'm wrong!): AnnotationDifferencer.java

[Ulli Hafner]

I think it would make more sense to run that part of your build in a profiler. Otherwise it is just a guessing since not every step in the plug-in uses logging statements. As far as I understand the message timestamps. It takes one minute from computing warning deltas and starting the task scanner. Does reference build #515 contain a lot of warnings? 

 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/00c23de9-84be-4764-8956-00f5d4c7db88%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ulli Hafner]

I think it would make more sense to run that part of your build in a profiler. Otherwise it is just a guessing since not every step in the plug-in uses logging statements. As far as I understand the message timestamps. It takes one minute from computing warning deltas and starting the task scanner. Does reference build #515 contain a lot of warnings