Performance issue since upgrade

SonarQube Server / Community Build
, ,
1

Hi @all, I recently updated my SonarQube Community instance deployed by Helm.

Here is my upgrade path (Helm chart) : 10.6.0 → 10.8.1 → 2025.1.5 → 2025.6.1

Database is PostgreSQL 14.

Plugins I use are :

  • sonar-dependency-check-plugin 6.0.0
  • sonar-findbugs-plugin 4.5.2
  • sonar-ansible-plugin 2.5.1
  • sonar-ansible-extras-plugin 2.5.1
  • sonarqube-community-branch-plugin 25.12.1 (from fabiogermann (fabio) · GitHub for the moment, I’m waiting for a release of mc1arke (Michael Clarke) · GitHub which is the version I use normaly)

The performance issue exists since version 10.8.1.

After this update, database upgrade was successful but the elastic search reindexing was very difficult. In fact, I had to increase the pod memory allocation a lot to allow reindexing to finish. It consumed up to 60Go memory !

For information, in the database, I have a project with a lot of branches/pull requests (most of them are 2 years old). I don’t understand because rules allow about 1 year max. This is another problem I have to check after (I already saw some posts regarding this issue).

For me, it’s the problemn but, despite this number of branches/pull requests, in 10.6, I had no performance issue.

Performance issue means it takes a long time to load when I go to the project page, when I list the branches/pull requests, when I delete a branch/pull request (about 5/6min !).

And when an analysis is running, memory grows a lot and in general, the sonar cli ends with a timeout (about 3min).

I checked a lot of posts but I didn’t find the solution.

I removed sonarqube-community-branch-plugin and sonar-dependency-check-plugin (because I found a post on that) but it’s the same.

Your help would be greatly appreciated.

Thanks !

Jérôme

2

Hi Jerome,

(Sorry about the missing accents. AmE keyboard :flushed_face: )

You list your current version as 2025.6.1. That means you’re using a commercial edition. Can you explain why you have felt the need to use the Community Branch plugin in addition. The point of that plugin is to appropriate the paid functionality of branch and PR analysis for Community Build users. As a commercial customer, you already have that functionality.

That said, because of the things that plugin does to accomplish its “appropriation” you’re kinda in an all-bets-are-off situation.

It sounds like housekeeping hasn’t been running properly to clean out old branches and PRs - not shocking IMO, given the circumstances - and you’re just bogging down under the weight of the data.

 
Ann

3

Hi Ann,

No problem for the accents :wink: .

I don’t use the commercial edition but the community edition as I wrote in my message.

I use the version 2025.6.1 of the Helm chart which uses the community version 25.12.0.117093.

Do you have any idea why housekeeping hasn’t been running properly ?

And why now, it’s a problem and not before ?

Thanks,

Jérôme

4

Hi Jerome,

No clue why housekeeping isn’t running. Unfortunately we can’t help you here with an instance compromised by appropriated functionality. You should ask the plugin maintainers.

 
Ann