With version 6.0 of SonarJava the analyzer was exchanged [1]. As per announcement a performance hit is to be expected. Did you estimate for some sample projects how long the analysis should take with the new scanner?
After switching to the new scanner, the time to analyze our projects increased from 3 hours to 41 hours. We had some issues before [2], but eventually those were solved. On SonarQube the analysis time increased, but not by much.
Version infos:
SonarQube Scanner 3.0.3.778
SonarQube server 7.9.1
SonarJava 6.0.1.20589
Enabling debug output didn’t yield any insights (we have some large files for which the ExplodedGraphWalker throws a MaximumStepsReachedException, but those files aren’t new). We have some custom rules which I could disable; the last time, though, it didn’t make a difference.
Just to be sure : are you using community edition of Sonarqube ? or another version ? (I’m searching for eventual usages of security rules).
Would it be possible for you to share the logs of analysis ? In order to understand where the time is spent (on which sensor).
We are using the Community Edition. Which logs do you need? Are the console output of the Jenkins job and the analysis.log from .scannerwork/scanner-report sufficient?
I have the same problem. Any solutions? According to the log, we can see the new version takes 2 seconds longer than the old one. 2020-04-02T16:00:00Ztest_6.7.txt (6.4 KB) test_7.9.1.txt (6.7 KB)
Version 6.3 of the Java Analyzer is about to be released (beginning of next week), and it should drastically improve performances, and restore it to a state similar to our 5.X serie. I would invite you to try again with it in a few days.