Uploaded image for project: 'SonarQube'
  1. SonarQube
  2. SONAR-12691

Optimise DB purge in Compute Engine

    Details

    • Type: Task
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Compute Engine, Database
    • Labels:
      None
    • Edition:
      Community
    • Production Notes:
      None

      Description

      The Compute Engine step "Purge db" can be optimised by dropping a few operations:

      • do not delete old records of ce_activity and ce_scanner_context┬ábecause they are already purged by the "startup leader" server on each new deployment
      • do not try to delete past measures of directories and files. Indeed the table project_measures contains only project measures.
      • do not persist the measures on new code in project_measures. They are never read and past measures require to be deleted on each new analysis. That generates a lot of IO in DB.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                simon.brandhof Simon Brandhof
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: