After upgrading to 9.9, analysis takes a long time

[Eunice]

Make sure to tell us:

• What version are you upgrading from? 8.9
• What’s the issue you’re facing?
  Users are complaining that after upgrading to 9.9, analysis takes a long time & log size is big.

Prod is 10 mins
Dev is 40 mins
Reports are generated in dev but they want to know why its taking longer time to run the analysis!

[Colin]

What database server is backing your SonarQube instance?

[Eunice]

@Colin

backing

Hi Colin,

We are using Postgres DB!

When user is running the analysis in Sonar Dev, the console logs runs until it reaches 2 GB and then it crashes the browser. When tried to enable debugging mode, it reaches 2.5 GB of data.
User is getting below error:
java.io.IOException: Cannot read more than 2Gib at a time

Concern has been raised that its because of the upgrade that logs files are increased as many parameters are being analyses!
Do we have any means to reduce the logs or is it because since he is running in dev for 1st time it might happen.

[Colin]

Hey there.

I’m getting a bit confused.

Which log file are you talking about? What is being logged?

I would also like to point you to this guide:

SonarQube becomes slow after PostgreSQL upgrade

Hello SonarQube Operators! It’s common that after performing an upgrade of PostgreSQL, a SonarQube instance connected to a PostgreSQL database can become painfully slow. Thankfully, we know how the issue can usually be addressed (it works almost every time!): by executing the following command against your Postgres database. VACUUM FULL ANALYZE For a PostgreSQL database, a VACUUM FULL command reclaims unused storage, while the ANALYZE command updates statistics used by the planner to determi…

[Eunice]

Hi Colin,

Am referring to the logs in the user side but not on Postgres or Sonar.
After users runs his analysis, log size is getting bigger. Do we have any parameters to be added to reduce the logging when running the analysis to generate the report in Sonar. USer is using Jenkins, when asked to use Sonar dev for UAT testing, he complains that logs are increased!

[Colin]

Hey there.

It’s still not clear which logs. Can you provide an example? Screenshot?

[Eunice]

Hi Colin,

These logs are not from Sonar server or Database.
One user has raised a concerns that after upgrading our Sonar in Dev, when running analysis in Jenkins will generate logs in Jenkins console. The logs size is larger than 2 GB after performing the upgrade. Wheras there were few parameters that he mentions are new in console output in Jenkins. Does Sonar upgradehave any impact in Jenkins console log size exceeding 2 GB!

[Colin]

This looks like somebody has DEBUG-level logs turned on in their Ant build ant -v or ant -verbose. SonarQube shouldn’t have any impact here.