ClosureJavascriptFramework icon indicating copy to clipboard operation
ClosureJavascriptFramework copied to clipboard

Published 20 hours ago • verified publisher icon jlgrock

Run Metrics on Compile

Open jlgrock opened this issue 12 years ago • 1 comments

Need to determine what is taking the longest amount of time to see if it can be sped up. For our larger projects, on a Windows environment, this can take up to 10 minutes to run. In Linux/Mac, this tends to take ~2 min.

jlgrock avatar May 22 '12 18:05 jlgrock

I have now run metrics. It seems that the majority of the time is experiences during the parsing of test results. I sped it up by stopping after 5 bugs (by default - this can be overridden). However, this has not significantly gained in performance (<5%). However, I was able to localize this. It is in the "parseFiles" method of the ClosureTestingMojo.java. When it calls the ParseRunner, it takes forever. Based on MAT and VirtualVM, this is not due to memory or CPU issues though.

Suggestions: This may need to be multithreaded or I/O performance checked (though I am using a Retina mac currently, so I/O should never be a problem - but that's an assumption, not a fact).

jlgrock avatar Aug 18 '12 20:08 jlgrock