Need suggestions on speeding up sonar

SonarQube Server / Community Build
1

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
  • how is SonarQube deployed: zip, Docker, Helm
  • what are you trying to achieve
  • what have you tried so far to achieve this

Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!

We are using Sonarqube 10.5 developer edition with the latest scanner.
We have a huge monorepo containing both the backend and the frontend code. Currently, we have analysis for the frontend disabled and it typically takes around 10-11 minutes for sonar analysis. However, with frontend analysis on, it increases to around 17-18 minutes. We are trying to speed this up. We are thinking of somehow enabling parallelization to speed up the analysis.
Can we create a separate project on sonarqube for our frontend code without actually separating the code in a different repo and run sonar analysis for backend and frontend in parallel?

I’m open to other suggestions on speeding up sonar.

2

Hey there.

What language (s) are you analyzing?

3

Hey Colin,
We are using Java in backend and vue js for frontend

4

I think a first good step would be to turn on the frontend analysis, and figure out which sensors are taking the longest.

Could you try to look at the time information in the analysis console?
For example:

# if you have saved your scanner logs in an analyze.log file
$ grep 'time=' analyze.log
...
INFO: Sensor JavaSquidSensor [java] (done) | time=210234ms
INFO: Sensor CSS Rules [cssfamily] (done) | time=3ms
INFO: Sensor C# Properties [csharp] (done) | time=0ms
INFO: Sensor SurefireSensor [java] (done) | time=0ms
INFO: Sensor JavaXmlSensor [java] (done) | time=16ms
INFO: Sensor HTML [web] (done) | time=4ms
...

In your case, you could probably filter by time with at least 6 digits:
$ grep -E 'time=[0-9]{6,}ms' analyze.log

Then if the analysis stays more than 10 seconds on a file, you can have duplicated lines like:

$ grep -E 'files analyzed, current file:' analyze.log
...
INFO: 1931/5345 files analyzed, current file: src/javax/xml/catalog/GroupEntry.java
INFO: 1931/5345 files analyzed, current file: src/javax/xml/catalog/GroupEntry.java
...

You can find them using:

$ diff <(grep -E 'files analyzed, current file:' analyze.log|sort) <(grep -E 'files analyzed, current file:' analyze.log|sort -u)
< INFO: 1931/5345 files analyzed, current file: src/javax/xml/catalog/GroupEntry.java

Could you share your bigger ‘time=’ log line?