have some kind of cache for frequently accessed blocks #179
Labels
No Label
AdminAPI
Bug
Check AWS
CI
Correctness
Critical
Documentation
Ideas
Improvement
Low priority
Newcomer
Performance
S3 Compatibility
Testing
Usability
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#179
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Blocks are addressed by their hash, the content can't be changed so it should be rather easy to cache (no cache invalidation required).
Having gateways that can cache frequenty used blocks could reduce the load on nodes storing these blocks.
For the first block of an object, it can probably reduce first byte latency by not paying the transfer time of the whole block before sending that first byte (still paying the rtt because version_table is consulted in parallel to fetching first block)