Long UI loading times since upgrade to 2025.1

[falco-bethke]

Ref: https://community.sonarsource.com/t/long-loading-times-at-project-dashboard-since-upgrade-from-9-9-6-to-2025-1/134871/2

during update and table migration the SQ webserver needs to be pushed to a max of several GByte Mem to not run in OutOfMem/heap errors

Sonar says:

This plugin stores the dependency-check HTML report in a measure. This report can get pretty large (multiple MB). Following the compression of live measures (introduced in 10.8), the endpoint causing your issues is retrieving all the measures of all the branches. So, for 130 branches, it can get pretty slow.
This is not what measures are intended to be used for, we will discuss internally if we should restrict the measures’ size.
In the meantime, if you don’t care about displaying the HTML report through the SonarQube UI, you could stop loading the property sonar.dependencyCheck.htmlReportPath. This will prevent the report from being loaded in a measure. As a middle-ground, you could choose to load it only for the main branch or some branches.
As you analyze the branches without the report, the measures and memory usage will return to normal, and you will no longer experience those slowdowns.

their suggestion:

either

• Remove the plugin
  or
• stop loading the analysis property sonar.dependencyCheck.htmlReportPath. If you do that you'll still have the issues and metrics created by the plugin. You just won't be able to access the HTML report in the project dashboard.

I think there is a lack of communication in how DepedencyCheck info is passed to SQ?!

[xtermi2]

This issue should be fixed in the next sonarqube patch release 2025.1.1
See also

• https://community.sonarsource.com/t/out-of-memor-after-updateing-9-9-10-8/131649/20
• and https://sonarsource.atlassian.net/browse/SONAR-24522