SonarQube 5.x performance changes

We currently use SonarQube 4.3.3 on a fairly big project with 30+ developers, 300k LOC, 2200 Unit Tests and it is currently used to help us tracking issues on our Continuous Integration cycle (Merge Requests, etc).

With the increase of custom XPath rules, we’re seeing a big increase on the analysis time. Moreover, we currently can’t run more than one analysis at the same time (the second one hangs on "waiting for a checkpoint from Job #xxx) so this usually makes things slow. We’re seeing build times (Jenkins + JUnit + SonarQube) around 30 minutes. With the release of the 5.x branch, we’d like to know if the effort to update everything is worth the while, so we’ve got some questions?

  1. Are Java rules faster than the old XPath rules to process?
  2. Will we be able to run more than one analysis at the same time?
  3. I saw on SonarSource’s JIRA that the 5.2 release (which will detach the analysis from the DB) is due to the 23rd of September. Will this really happen? Are the users expected to see a big performance increase with this?

We’re curious to hear real-world cases on this, so any input will be highly appreciated.


Hi @likith_sunny,

if you are running SonarQube 4.3, you are years late now on our current supported version of SonarQube. The current LTS is 7.9 and the latest version is 8.6…
I would highly recommend you to upgrade or, even better, to start a new SonarQube server from scratch on our latest version - to avoid upgrade paths that could take time (from 4.3 --> 5.6 --> 6.7 --> 7.9 LTS --> 8.6).

Then, you’ll see the differences with SonarQube integration, MR decoration (included natively in SonarQube with Gitlab in 8.X series, if you use a Developer Edition at least)…




To augment Carine’s excellent answer:

Yes. And you need to be ready to implement a custom plugin. Also, hundreds of rules have been added since 4.3. You may find that what you need is provided by default. If not, I would ask myself how important those other rules really were.


Uhm… 5.2 released in November of 2015.

You need to upgrade to a current version, as detailed above by Carine, immediately.