Hi @all,
we’ve been experiencing the same issue lately.
Apparently, if in SonarQube the background tasks take too long, it indicates a DB problem because SonarQube relies on the DB performance.
Our Azure’s DB dashboard showed that the DB IOPS were > 90% last week.
Our Datadog metrics showed that last week processing_time & process_pending_time had an unusually high peak.
We are using Azure Postgresql DB General Purpose, 2 vCore(s), 50 GB. 68% of the storage was used. The IOPS scale with the provided storage size in a ratio of 3:1.
What did you change?
We scaled up the DB to 100GB, we now have 300IOPS instead of 150IOPS according to the Azure docs.
The problem still occurs in our pipelines, is this a bug?
As you can see after optimizing the DB the performance seems to have recovered however the publish time still takes way too long!
![]()
Sonarqube Background Tasks:

