did some tests with the new SonarJava 6.0.1 (build 20589) and i can confirm @pranav-jobvite findings.
Used our most problematic Java legacy project for an initial scan.
Sonarqube 8.1 (build 31237) with SonarJava 6.0.1 (build 20589)
Total time: 305 minutes 41 seconds
Sonarqube 8.1 (build 31237) with SonarJava 5.14 (build 18788)
Total time: 83 minutes 44 seconds
It means it’s even more than 3x times, this is a showstopper even if more issues are found
As this was an initial scan, the git blame took a lot of time.
Are there any investigations going on in that area, found only
but nothing new.