Cache SonarCloud analysis reports for performance improvement

[anon22666463]

Hi,

we’re using SonarCloud analysis for every pushed git commit. So for every commit there’s > 4000 files scanned, which takes ~ 10 minutes per analysis.
Is there a possibility to cache the analysis results in order to only rescan files that changed since the last scan and therefore achieve significant performance improvements?

If not, is there any other way in improving the speed of the analysis? The project has ~ 100.000 lines of java code and the scan runs on a machine with 2 CPUs and 3 GB memory.

Cheers,
Patrick

[Quentin (Quentin Jaquier)]

Hello,

I believe you are talking about what we call “incremental analysis”, you can therefore have a look here:

Incremental Scan support

Must-share information (formatted with Markdown): SonarQube 7.6 with SonarQube-GitLab plugin Faster build and scan for our GitLab merge request process Removed unnecessary files and tests Hello, we are trying to implement merge request scanning in our GitLab CI process, and the scanner is reaching around 17 minutes to scan our 603k LOC project. Is there a way to implement incremental scanning so that SonarQube will not index and scan all files in the project and only scan the changed files? T…

Concerning other way to improve performance, I don’t see any quick win in your case.
As pointed out in the other thread, there is already a ticket with the goal of speeding up SonarJava 6.x and the team will work on finding a solution.

Hope it clarifies the situations,

Quentin

[anon22666463]

Hi @Quentin ,

yes, the “incremental analysis” sounds exactly what I’m looking for.
We’re using SonarCloud and I’m not sure which version this actually means. I wasn’t able to find any information on that. Is there a way to see to which SonarQube version SonarCloud is actually running?

Thanks for the information!

Cheers,
Patrick

[Quentin (Quentin Jaquier)]

which SonarQube version SonarCloud is actually running?

There is no such notion.
In your context, I believe the question should be:

which SonarJava version SonarCloud is actually running?

And the answer is that, in SonarCloud, you will benefit from all the features that we deploy continuously automatically. You are therefore always using the latest version of Java analyser.

For more informations you can have a look there:

SonarCloud vs SonarQube

Hi Sonar Community, We are a small software company and we are planning to onboard Sonar as a code review tool. Now based on what we have seen so far, the pricing for SonarQube and SonarCloud seems identical (yearly vs monthly x12 ) . So what exactly is the difference between the 2 of them? Just that the code review is run on our server (Sonarqube) and on Sonar servers (Sonarcloud) ? Any help is greatly appreciated

[Alexandre_Gigleux]

Hello @anon22666463,

While we are working to implement incremental analysis on PR for Java, we also work to improve the raw analyzer speed.
We just released a new version which accept a property sonar.java.experimental.batchModeSizeInKB activating an experimental feature keeping more data in memory which has a significant impact on the speed of analysis for Java projects (between 10 to 90% increase according to our tests).

Would you be OK to test this property and share a before / after comparison?

You can start with sonar.java.experimental.batchModeSizeInKB=1024 and increase it gradually.

Thanks
Alex