Could calculate a score for each entry (perhaps score = time-to-create / size / time-since-use) and choose not to cache items below some score threshold, and remove items with the lowest score when the cache reaches a pre-configured size.
(#99 #103)
Allow transforms to configure caching
Transforms should be able to mark themselves as cache disabled, cache forced etc.
Consider best way to configure cache sizing
As of #103 cache target size is configured as part of the cache itself. We may want to move this to the site.yaml but that could vary by configuration. Perhaps a user.yaml is needed?
Consider when/how to clear old cache
Could calculate a score for each entry (perhaps score = time-to-create / size / time-since-use) and choose not to cache items below some score threshold, and remove items with the lowest score when the cache reaches a pre-configured size. (#99 #103)
Allow transforms to configure caching
Transforms should be able to mark themselves as cache disabled, cache forced etc.
Consider best way to configure cache sizing
As of #103 cache target size is configured as part of the cache itself. We may want to move this to the site.yaml but that could vary by configuration. Perhaps a user.yaml is needed?