Sonar

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4, 1.5
• Fix Version/s: 1.5
• Component/s: None
• Labels:

  None

Here are several tips to greatly improve Sonar database use by reducing the number of rows in project_measures table :

• For each couple "class/rule" or "class/rules category" there are currently 6 measures whereas two are really used (Violations on mandatory rules and Violations on optional rules)
  • Stop calculating the others four measures (Coding rules compliance, Optional coding rules compliance, Coding rules compliance, including optional rules, Violations, including optional rules)
  • 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 entity from 700 to less than 100 and perhaps a lot less ...

To evaluate improvements, launch Sonar on STRUTS 1.3.9 source code. With version 1.5M2, 427'000 rows are inserted in project_measures table (290'000 with version 1.4.2), after those improvements, we should fall to ... let's say less than 70'000 rows.

• Assignee:

  Simon Brandhof

  Reporter:

  Freddy Mallet

• Created:

  29/Nov/08 3:13 AM

  Updated:

  15/Mar/09 1:29 PM

  Resolved:

  03/Dec/08 4:01 PM