Slowdown in Gitlab job with SonarQube Enterprise

Hello, We are using SonarQube Enterprise and recently we have witnessed a huge slowdown in out Gitlab build

The typical values before

INFO: Load/download plugins (done) | time=105837ms
INFO: Load/download plugins (done) | time=255914ms
Has degraded to
INFO: Load/download plugins (done) | time=723776ms (since the last 3 days, it is taking a lot longer)

INFO: SonarScanner
INFO: Java 1.8.0_312 Private Build (64-bit)
INFO: Linux 5.4.0-1038-aws amd64


  • Enterprise Edition * Version 8.9.5 (build 50698)

Could there be any other reason other than network throttling to explain such behaviour?


The network is the first place I would look.

You might also check the load/resources on the box hosting SonarQube. I can’t see any reason SonarQube would respond to requests more slowly, but maybe it doesn’t have the resources to respond quickly…?


Hi Ann,

Thanks. Indeed I will try to get the network team to trace the calls and send back a report, so we have more data to do a proper analysis.

I am also having a hard time getting the cache to work, since we have 32 Gitlab runners that don’t share cache and these are rotated every week.

1 Like

@ganncamp the timings provide in debug mode are supposed to indicate the completion of the download of the plugin or the handling of the connection?

DEBUG: GET 200 https://sonarqubeserver/api/plugins/download?plugin=java&acceptCompressions=pack200 | time=43ms


I believe it’s the time it took the task to complete, so in this case, that’s how long that individual download took.


P.S. You may find this thread interesting:

1 Like