feat: implement LRU TTL refresh for S3 cache on Open#173
Open
feat: implement LRU TTL refresh for S3 cache on Open#173
Conversation
Like the disk cache, S3 now resets the expiration time on each Open (read) using server-side copy-to-self with metadata replacement. This prevents frequently accessed snapshots from expiring while periodic snapshot jobs handle content freshness. Co-authored-by: Amp <amp@ampcode.com> Amp-Thread-ID: https://ampcode.com/threads/T-019cda52-ee36-738c-86cd-1fd410c47d7f
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
S3 cache entries expire based on creation time (fixed TTL). Frequently accessed snapshots expire after 72h regardless of usage, causing cold cache misses after pod restarts when no periodic jobs are running to refresh them.
Solution
Like the disk cache, S3 now resets the expiration time on each
Openusing a server-side copy-to-self with metadata replacement (CopyObjectwithReplaceMetadata). No data is re-uploaded — only theExpires-Atuser metadata is updated.Content freshness is still handled by periodic
generateAndUploadSnapshotjobs (every 1h) which overwrite the S3 entry with a fresh snapshot from the latest git state.