Uploaded image for project: 'PuppetDB'
  1. PuppetDB
  2. PDB-3695

Package GC spends a lot of time when there's probably very little to clean up

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • None
    • PDB 5.2.0
    • PuppetDB
    • PuppetDB
    • Needs Assessment
    • Normal
    • 2 - 5-25% of Customers
    • 3 - Serious
    • 4 - $$$$$
    • Hide
      It seems like this would hit some of the largest users of PDB but most users who are not bottlenecked at the database won't notice it. It would be nice to have these tunings. As more customers move onto versions with package inspector the priority of this may increase.
      Show
      It seems like this would hit some of the largest users of PDB but most users who are not bottlenecked at the database won't notice it. It would be nice to have these tunings. As more customers move onto versions with package inspector the priority of this may increase.
    • Bug Fix
    • Improve package GC in PuppetDB. This patch improves a query used to target packages for deletion.
    • Needs Assessment

    Description

      The Problem

      In our own PE install, we see that package GC spends 3-4 minutes every hour. Since package GC rarely needs to clean up anything it should not run with every GC interval.

      The solution

      I don't see a way to make the query any faster. Here's a query plan:

      https://explain.depesz.com/s/WjzV

      So, I suspect the solution is just to run different parts of GC at different times instead of lumping them all together. That's PDB-2428.

      Workaround

      https://forge.puppet.com/npwalker/puppetdb_gc.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              nick.walker Nick Walker
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support