Hi, After upgrading from version 8.0 to version 8.9 (Community Edition), some tasks (not all, only some of them) are processed for a very long time (some tasks that took before seconds, is very slow now, and complete in tens of minutes, and some in several hours). It was found that this is due to …

Hi Sylvain, After getting over the CE logs again, it became clear that I was mistaken with the definition of the problem at the beginning. The real cause of the issue is that complex database queries take too long to execute. So, after tuning the postgresql configuration (in my case, increasing the…

Hello @Alexander_Dragun and welcome to the Community! From your report, I understand that you are experiencing some problems with the speed of some Analysis Background tasks on SonarQube server side, and not one code analysis (which is run with the scanner in your pipeline build agents). And you …

Hi, Sylvain, much thanks for your response! Yes, we applied VACUUM; All right, the problem is observed on the server side, but not with all the tasks. In the CE trace log, we can see that some requests were processed much longer than before.

Also most commonly, but not always, it happens with new branches.

Hi @Alexander_Dragun thanks for the clarification. Java application slowness is very often (but not always) due to memory limits. You may have a look at the CE and ES JVM memory consumption and settings, and at the SonarQube Memory Tuning Guidelines in order to check this. And branch analysis wit…

Also, after reading the documentation, I still have a question: does Elasticsearch participate in the background task processing process? Or is it only involved in processing WEB server requests?

Right now: 2021.06.02 11:49:39 TRACE ce[AXnMEHjmaQpQKEvCLH4K][o.s.c.t.p.i.IntegrateIssuesVisitor] Visiting component SOME-PROJECT:prj-srv/src/main/resources/templates/2_2_SUBMIT_PROJECT.html:BRANCH:fixbug-SOMEPROJECT-8323-fe (done) | time=60213ms

Hello @Alexander_Dragun the Compute Engine will both read from and write to the Search component during the Project Analysis background task. Elasticsearch cache data is used as well (read from) by the Web component. You may have a look at heap memory settings and current usage for all your Sonar…

Hi) Web JVM State Max Memory (MB) 1024 Free Memory (MB) 328 Compute Engine JVM State Max Memory (MB) 512 Free Memory (MB) 386 Search Engine JVM Heap Usage 19.0% JVM Heap Used 192 MB JVM Heap Max 989 MB

You should definitely extend the memory for the Compute Engine, 512MB is too little. 1GB should be considered a very minimal value for this component (this is what I use on my laptop test instance). If you don’t have sufficient memory on your SonarQube server, you can temporarily reduce the memory …

That’s great. And thanks for sharing!

Slow analysis of Code after upgrade

SonarQube Server / Community Build

Alexander_Dragun (Alexander Dragun) June 2, 2021, 12:08pm 9

Hi)

Web JVM State

Max Memory (MB)	`1024`
Free Memory (MB)	`328`

Compute Engine JVM State

Max Memory (MB)	`512`
Free Memory (MB)	`386`

Search Engine

JVM Heap Usage	`19.0%`
JVM Heap Used	`192 MB`
JVM Heap Max	`989 MB`

Task execution extremely slow after postgres upgrade

Topic		Replies	Views
Analysis report processing takes too long for some projects SonarQube Server / Community Build	6	449	May 9, 2023
Server side analysis slow after update from v9.9.1 LTS to v10.5.1 (Enterprise) SonarQube Server / Community Build	16	502	January 8, 2025
Very slow analysis after 8.1 -> 8.8 upgrade SonarQube Server / Community Build sonarqube , performance	5	3294	June 3, 2021
Task execution extremely slow after postgres upgrade SonarQube Server / Community Build sonarqube , postgres	3	1178	October 5, 2021
Very slow analysis of code SonarQube Server / Community Build	2	932	June 26, 2020

Slow analysis of Code after upgrade

Web JVM State

Compute Engine JVM State

Search Engine

Related topics