Analysis times almost doubled

[copy (Christian Scharkus)]

Hello,

we’re using SonarQube CE Version 7.9.2 (build 30863) with Jenkins and maven (sonar-maven-plugin 3.7.0.1746) to analyse our project.

I recently noticed that the analysis time on the sonar server increased (from about 15 minutes to now 50).

There seems to be a problem with the database (we’re using postgres) because theres a thread using 100 percent cpu at times and persistence as per the logs takes a long time.
Do you have any tips how to improve database performance?

The other thing I noticed in the log is that the step “Build tree of components” takes about 20 minutes. What exactly does that do and is there a way to speed that up somehow?

Here’s the log of the most recent analysis:
sonarqube_ce_20200324.log.txt (8.1 KB)

[ganncamp (G Ann Campbell)]

Hi,

Welcome to the community!

How recently did you notice this change? Was it right after a server upgrade? The Upgrade Procedure advises that you may want to perform some Additional Database Maintenance after an upgrade…

 
HTH,
Ann

[copy (Christian Scharkus)]

Hi,

thanks for your response

There wasn’t a server update since we’re running the LTS version. I’ll look into doing the database maintenance just to make sure.

[Rebse (Gilbert Rebhan)]

Hi,

i guess you’ve updated the SonarJava scanner from 5.x to 6.x !?
There are known performance issues after migration to Eclipse compiler frontend.
Because of this we’re still using SonarJava 5.14 (build 18788) in production.
see

SonarJava 6.0.1 3 times slower than 5.14

Hi Alex, 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 in…

and the relevant Sonarsource Jira ticket Log in - SonarSource

Gilbert

[sonarcode92923]

Kind of same topic here… experts tell me analysis runs up to 30+ Mins. plus mention ‘round-trips’ if SQ fails on master branch on top of pipeline which takes nearly 20 Mins… how can this be optimized? Thanks

[copy (Christian Scharkus)]

Hi,

in my case it was the databases fault. Our admins didn’t setup the cleanup right.
After a postgres vacuum the background task duration went down to 2 seconds.

sincerely,
Christian

[sonarcode92923]

Thanks Christian, I will forward this information.