HomePhorge

Caching node information in yaml (I figured caching in memory will cause ever…
4a45a1da0653Unpublished

Unpublished Commit · Learn More

Repository Importing: This repository is still importing.

Description

Caching node information in yaml (I figured caching in memory will cause ever-larger memory growth), and changing the external node terminus to use the version of the facts as their version. This will usually result in the cached node information being used, instead of always hitting the external node app during file serving. Note that if the facts aren't changed by the client, then this will result in the cached node being used, but at this point, the client always updates its facts. (#1130)

Details

Provenance
Luke Kanies <luke@madstop.com>Authored on
vanmeeuwenPushed on Jun 2 2015, 2:22 PM
Parents
rPUf3a304c557c0: Modifying the yaml terminus base class to use the timestamp of the yaml file…
Branches
Unknown
Tags
Unknown

Event Timeline