Details
-
Type:
New Feature
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 3.6
-
Component/s: None
-
Labels:None
Description
When this option is activated, we expect to get the following log at the end of the batch execution (when the project contains several modules we should get this both at the end of the module and project exection) :
- Decorators execution time : 1mn 23s <- sorted by execution time
- Sensors execution time : 45s
- Post-Jobs execution time : 35s
- Sensors execution time breakdown
- JavaSquidSensor : 72ms <- sorted by execution time
- CheckstyleSensor : 10s
- ...
- Decorators execution time breakdown
- ViolationTrackingDecorator : 23s
- EventDecorator: 21s
- ..
- Post-Jobs execution time breakdown
- Views : 20s
- DeveloperCockpit : 10s
- DBCleaner : 5s
Moreover on the DBCleaner we expect to see the time required to purge each table: duplications_index, dependencies, ...
Attachments
Issue Links
- is duplicated by
-
SONAR-4142 In Sonar verbose mode we should display the time required to purge each table: duplications_index, dependencies, ...
-
- Closed
-
- is related to
-
SONAR-3340 The purge time can be a bit long (several minutes) when the cross-project duplication detection mechanism is activated and MySQL is used
-
- Closed
-
-
SONAR-4384 When dumping profiling information with help of the 'sonar.showProfiling' property, some Sonar phases are missing
-
- Closed
-
- relates to
-
SONAR-5808 Dump profiling results in a file
-
- Closed
-