Upgrade from 6.7.6 to 7.6 Community significantly slower

We have been experiences a large backlog due to what we believe is the Persist Live Measures process since upgrading from 6.7.6 to 7.6.

This has created a backlog of scans and doubling the amount of times the our build scans take.

We have beefed up our servers to twice the heap, memory, and processing power, however this does not seem to affect the scan time. We have also created a quality gate that will pass anything, this also has not affected the build time.

A partial log is below, is there any information on why Persist Live Measures is taking so long to process?

2019.05.03 07:56:04 INFO ce[AWp99a31JnwnERbDKTig][o.s.c.t.s.ComputationStepExecutor] Persist components | status=SUCCESS | time=237ms
2019.05.03 07:56:04 INFO ce[AWp99a31JnwnERbDKTig][o.s.c.t.s.ComputationStepExecutor] Persist analysis | status=SUCCESS | time=2ms
2019.05.03 07:56:04 INFO ce[AWp99a31JnwnERbDKTig][o.s.c.t.s.ComputationStepExecutor] Persist analysis properties | status=SUCCESS | time=2ms
2019.05.03 07:56:04 INFO ce[AWp99a31JnwnERbDKTig][o.s.c.t.s.ComputationStepExecutor] Persist measures | inserts=72 | status=SUCCESS | time=6ms
2019.05.03 07:59:51 INFO ce[AWp99a31JnwnERbDKTig][o.s.c.t.s.ComputationStepExecutor] Persist live measures | insertsOrUpdates=1540 | status=SUCCESS | time=227207ms
2019.05.03 07:59:51 INFO ce[AWp99a31JnwnERbDKTig][o.s.c.t.s.ComputationStepExecutor] Persist new ad hoc Rules | status=SUCCESS | time=0ms
2019.05.03 07:59:51 INFO ce[AWp99a31JnwnERbDKTig][o.s.c.t.s.ComputationStepExecutor] Persist issues | inserts=0 | updates=0 | merged=0 | untouched=49 | status=SUCCESS | time=24ms
2019.05.03 07:59:51 INFO ce[AWp99a31JnwnERbDKTig][o.s.c.t.s.ComputationStepExecutor] Persist project links | status=SUCCESS | time=4ms
2019.05.03 07:59:51 INFO ce[AWp99a31JnwnERbDKTig][o.s.c.t.s.ComputationStepExecutor] Persist events | status=SUCCESS | time=4ms

What database engine / version?

Also, which edition?

 
Thx,
Ann

MMSQL 2016 13.0.4451

2016 SP1 CU5, is this what you are looking for?

Thanks for the response. It’s not actually what I was looking for. Specifically, I’m wondering if you have Enterprise Edition, and so Portfolios in the mix.

Or is that log snippet from a project?

 
Thx,
Ann

It is a Community version. The snippet is from a project scan taken from the ce.log.

Michael,

I would check in on a couple things on the database/network side. The Compute Engine is database-intensive, so most performance is to be gained by paying attention to the database.

Keep an eye on–

  • Up-to-date indexes and statistics
  • Network latency between the SonarQube server and the Database server
  • Resource consumption of the database server

Any database performance monitoring available to you might reveal where the holdup is (deadlocks, waiting, resources). We don’t have exact performance benchmarks for this step, but ~227 seconds for 1,540 inserts/updates seems a bit too long. For example, I have a support case open with a customer who has ~45k inserts/updates and this step is taking 90 seconds (and is also MSSQL)

Colin

1 Like

Thank you for the information. I will work with our network and database people to see if we can come up with something.