Details
Improvement
Critical
Description
Whereas SONAR-487 was dedicated to improve Sonar database use on class measures, this new improvement focus on other kind of resources (projects, modules, packages).
Here is a tip to improve Sonar database use by reducing the number of rows in project_measures table for this king of resources :
- For each couple "resource/rule" there are currently 6 measures whereas two are really used (Violations on mandatory rules and Violations on optional rules)
o Stop calculating the others four measures (Coding rules compliance, Optional coding rules compliance, Coding rules compliance, including optional rules, Violations, including optional rules)
o For the two remaining measures, they should be filled only when the value is not 0
Those improvements should reduce the number of measures by resources (projects, module, package) from 700 to less than 100.
With this new improvement, I think we can divide the number of rows in project measures by 2.
Issue Links
| This issue relates to: | ||||
| SONAR-487 | Improve Sonar database use on class measures (project_measures table) |
|
|
|
I've done my benchmark.
With this new improvement, the project_measures table will contain 12'933 rows associated with project STRUTS-1.3.9.
There were
and so 12'933 once this ticket will be fixed
- 290'000 rows with Sonar 1.4
- 427'000 rows with Sonar 1.5 Milestone 1
- 53'000 rows with Sonar 1.5 Release Candidate 1
and so 12'933 once this ticket will be fixed