Project Analysis has gone from taking <10 minutes to 1-4 hours

SonarQube
1

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
    • SonarQube 8.9.2.46101
  • what are you trying to achieve
    • Normal analysis times
  • what have you tried so far to achieve this
    • Increased heap size

In the logs for all of the compute engine jobs that take a long time, all/most of the time is spent on “Execute component visitors”
INFO ce[AX_xlp9P507dhfHbU1a7][o.s.c.t.s.ComputationStepExecutor] Execute component visitors | status=SUCCESS | time=1149574ms

2

Hi,

Welcome to the community!

The timing in the log line you’ve shared translates to about 20min. I guess others are longer(?).

Are the projects where you’re seeing this particularly large?

Also, could you (briefly) turn on DEBUG logging while one of the slower projects is processed & post that log?

 
Ann

3

Hi, thanks for the quick response!

Yes, I picked the wrong line. Here is a longer one from this morning

2022.04.05 05:47:05 INFO  ce[AX_5Hha2DSZawtEaznuj][o.s.c.t.s.ComputationStepExecutor] Compute Quality Profile status | status=SUCCESS | time=16ms
2022.04.05 09:20:42 INFO  ce[AX_5Hha2DSZawtEaznuj][o.s.c.t.s.ComputationStepExecutor] Execute component visitors | status=SUCCESS | time=12817535ms

This job ran from 5:46:13 AM to 9:23:36 AM

This is happening on all our projects regardless of size (picking 3 examples 30k, 125k and 300k LOC)
I have now turned on debug logging, if anything new is logged I can post it.

1 Like
4

Here is the debug output

2022.04.06 03:34:43 INFO  ce[AX_6aIETDSZawtEaznvC][o.s.c.t.s.ComputationStepExecutor] Compute Quality Profile status | status=SUCCESS | time=22ms
2022.04.06 05:19:42 DEBUG ce[AX_6aIETDSZawtEaznvC][o.s.c.t.p.s.ExecuteVisitorsStep]   Execution time for each component visitor:
2022.04.06 05:19:42 DEBUG ce[AX_6aIETDSZawtEaznvC][o.s.c.t.p.s.ExecuteVisitorsStep]   - LoadComponentUuidsHavingOpenIssuesVisitor | time=8472ms
2022.04.06 05:19:42 DEBUG ce[AX_6aIETDSZawtEaznvC][o.s.c.t.p.s.ExecuteVisitorsStep]   - IntegrateIssuesVisitor | time=6289895ms
2022.04.06 05:19:42 DEBUG ce[AX_6aIETDSZawtEaznvC][o.s.c.t.p.s.ExecuteVisitorsStep]   - CloseIssuesOnRemovedComponentsVisitor | time=1ms
2022.04.06 05:19:42 DEBUG ce[AX_6aIETDSZawtEaznvC][o.s.c.t.p.s.ExecuteVisitorsStep]   - MaintainabilityMeasuresVisitor | time=28ms
2022.04.06 05:19:42 DEBUG ce[AX_6aIETDSZawtEaznvC][o.s.c.t.p.s.ExecuteVisitorsStep]   - NewMaintainabilityMeasuresVisitor | time=94ms
2022.04.06 05:19:42 DEBUG ce[AX_6aIETDSZawtEaznvC][o.s.c.t.p.s.ExecuteVisitorsStep]   - ReliabilityAndSecurityRatingMeasuresVisitor | time=5ms
2022.04.06 05:19:42 DEBUG ce[AX_6aIETDSZawtEaznvC][o.s.c.t.p.s.ExecuteVisitorsStep]   - NewReliabilityAndSecurityRatingMeasuresVisitor | time=6ms
2022.04.06 05:19:42 DEBUG ce[AX_6aIETDSZawtEaznvC][o.s.c.t.p.s.ExecuteVisitorsStep]   - SecurityReviewMeasuresVisitor | time=3ms
2022.04.06 05:19:42 DEBUG ce[AX_6aIETDSZawtEaznvC][o.s.c.t.p.s.ExecuteVisitorsStep]   - NewSecurityReviewMeasuresVisitor | time=2ms
2022.04.06 05:19:42 DEBUG ce[AX_6aIETDSZawtEaznvC][o.s.c.t.p.s.ExecuteVisitorsStep]   - LastCommitVisitor | time=0ms
2022.04.06 05:19:42 DEBUG ce[AX_6aIETDSZawtEaznvC][o.s.c.t.p.s.ExecuteVisitorsStep]   - MeasureComputersVisitor | time=1ms
2022.04.06 05:19:42 INFO  ce[AX_6aIETDSZawtEaznvC][o.s.c.t.s.ComputationStepExecutor] Execute component visitors | status=SUCCESS | time=6298552ms

This one ran in total from 3:33:49 AM to 5:21:45 AM

5

Hi,

Thanks for collecting these logs!

I’ve flagged this for more expert attention. I suspect they’ll ask you to do some data gathering against the DB, but let’s see.

 
Ann

6

Thanks, I just learned we have paid support so I’ve opened a ticket SUPPORT-31210

1 Like
9

Closing it because paid support ticket has been created