Sonar scanning taking long time in version 10.6.0.92116

SonarQube Server / Community Build
1

SonarQube - 10.6.0.92116
SonarQube deployed: zip
Edition - Community
Scan time increased significantly.

Hello,

We were using Sonarqube version - 10.2.1.78527 and the scan time for the projects was around 1 to 2 minutes but from 19th August scan time increased significantly, from 1-2 minutes to 7-8 minutes. (No change in infrasturcute/ application)

On 24th August we upgraded the Sonarqube version to the latest 10.6.0 as previous versions are archived (10.3, 10.4) but the scan time is still long

We have checked the infrastructure part and resource utilization is OK, and there is no other change from our end

Can you please help us identify the issue with long-running scans

2

DB we are using PostgreSQL - 14.12

The similar issue we face with long-running scans in version “10.1.0.73491” it was resolved by upgrading to 10.2.1.78527, but now we are on the latest version.

3

Hi,

The potential variables are:

  1. changes in the code being analyzed
  2. changes to the build agent
  3. changes to the scanner
  4. an upgrade to SonarQube

Your “No change” assertion rules out pretty much everything. Are you sure that nothing on the build agent changed? Maybe there’s more load / less memory & CPU available? Did you upgrade the scanner?

Can you produce a debug analysis log to see where the time is being spent in the analysis?

The analysis / scanner log is what’s output from the analysis command. Hopefully, the log you provide - redacted as necessary - will include that command as well.

This guide will help you find them.

 
Ann

4

Hello Ann,

Thank you for your response

  1. changes in the code being analyzed - No change
  2. changes to the build agent - No change
  3. changes to the scanner - No change
  4. an upgrade to SonarQube - We were using Sonarqube version - 10.2.1.78527 and the scan time for the projects was around 1 to 2 minutes but from 19th August scan time increased significantly, from 1-2 minutes to 7-8 minutes.

Then we upgraded to the latest version 10.6, but the scan time was the same.

(The similar issue we face with long-running scans in version “10.1.0.73491” was resolved by upgrading to 10.2.1.78527)

We have run a Full vacuum analysis on DB, and the scan time looks good!

VACUUM FULL VERBOSE ANALYZE

Thank you!

1 Like
5

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.