Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-1699

Cache environments

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 3.6.0
    • Component/s: Docs
    • Labels:
      None
    • Template:
    • Story Points:
      3
    • Sprint:
      Week 2014-4-23 to 2014-4-30, Week 2014-4-16 to 2014-4-23, Week 2014-4-30 to 2014-5-7

      Description

      Currently, the new directory environments are not cached - each catalog compilation will start from scratch and reparse all puppet manifests and reload types.

      This can be solved by caching the result. A naive implementation that never evicts anything proved this to have a positive effect, bringing down the execution time to about 50% of the first compilation - and to a level on par, or slightly better than 3.4.2.

      The task consists of two things:

      • Make tests run - there are many tests that are written in a way that they rely on side effects / order of execution of settings / application of modulepath etc. This will take quite some time to untangle.
      • Cache eviction - while the naive implementation is on par with what 3.4.3 does (its cache does not evict either), we should at least explore if there is a suitable eviction algorithm that can be used (perhaps if the environment's directory does no longer exist)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              joshua.partlow Joshua Partlow
              Reporter:
              henrik.lindberg Henrik Lindberg
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support