Performance issue with SonarQube Developer's Edition

SonarQube Server / Community Build
1

Must-share information (formatted with Markdown):

  • We are using SonarQube Developer Edition Version 8.9 (build 43852)
  • We did not realize that it only provides single thread to do the static code analysis for Pull Requests and main code branch which has become a bottleneck/performance issue and our CI duration has increased exponentially impacting our developers productivity significantly. Please let us know how can we run multiple threads for the analysis with our existing Developer’s edition. It is currently hindering us to move forward with SonarQube and we may have to stop using it. Please note that we cannot upgrade to Enterprise edition immediately due to budget constraints as we only budgeted for Developers Edition.
    we did not realize that it only provides single thread to do the static code analysis for Pull Requests and main code branch which has become a bottleneck and our CI duration has increased exponentially impacting our developers productivity significantly. Please let us know how can we run multiple threads for the analysis with our existing Developer’s edition. It would be great if someone can propose us a workaround or solution to the performance issue we are facing as it is hindering us to move forward with SonarQube and we may have to stop using it. Please note that we cannot upgrade to Enterprise edition immediately due to budget constraints as we only budgeted for Developers Edition.
1 Like
2

Hi,

Welcome to the community!

Since upgrading to Enterprise Edition($$) isn’t in the budget right now, your next best option is to put more power under SonarQube so its single thread runs faster. Once you’ve got a powerful processor & plenty of memory under SonarQube, you can tune the *.javaOpts properties - specifically sonar.ce.javaOpts in $SONARQUBE-HOME/conf/sonar.properties to make sure all that horsepower is actually used. (The CE/Compute Engine process is the one that handles processing of analysis reports.)

 
HTH,
Ann

1 Like
4

Hi @ehaider ,

were do you have you bottle neck? Really on the processing of thre repots on SonarQube server?

For us it is more a problem on the scanners during analysis, where we would like to see faster processing (mightby multithreading, I only know the C++ scanner has explicit option to set the number of threads). And at least to my understanding, EE wouldn’t bring you additional speed on the scanners.

2 Likes