Sometimes, it needs much time for special step of PR/Branch analysis

SonarQube
1

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
    INFO: SonarScanner 4.7.0.2747

Sometimes sonarscanner spents much time like this.
There is any point to tune up?

First try

[2023-03-09T08:55:48.386Z] INFO: Load active rules
[2023-03-09T08:55:49.729Z] INFO: Load active rules (done) | time=1337ms
[2023-03-09T08:55:49.729Z] INFO: Load analysis cache
[2023-03-09T08:55:49.979Z] INFO: Load analysis cache | time=69ms

Second try – it spents much time. 1.3s <->242s 0.07s ↔ 417s

[2023-03-09T23:33:51.406Z] INFO: Load active rules
[2023-03-09T23:37:57.656Z] INFO: Load active rules (done) | time=242047ms
[2023-03-09T23:37:57.656Z] INFO: Load analysis cache
[2023-03-09T23:45:03.911Z] INFO: Load analysis cache | time=417201ms

These two builds are in the same branch analysis.

image
image1064×345 19.7 KB

2

Hi,

What’s your SonarQube server version? If you’re not sure, you can check the page footer.

Do you have anything “helpful” on your network between SonarQube and Jenkins that might be interfering?

Could you check your server logs logs and see if the slowdown you’re seeing in analysis correlates with anything in particular on the server side? I would expect this to show up - assuming anything does - in the ce.log or web.log.

 
Ann

3

Dear Ann,

Thank you for your response.

SonarQube version:

  • Developer Edition Version 9.9 (build 65466)

Network:
sonarqube and jenkins is installed in same server with saperated docker container.
I believe there is no issue caused by network environment.

Server log
I attached them.
web.2023-03-09.log (244 Bytes)
ce.2023-03-09.log (95.2 KB)

4

Hi,

Your server logs won’t do me much good since I don’t have the timestamps of the slowdowns. I need you to check them to see if you can correlate anything unusual at the server with a slowdown in Jenkins.

 
Ann