Feature #18961
open
Go FileSystem / FUSE mount supports block prefetch
Added by Peter Amstutz over 1 year ago.
Updated 8 days ago.
Estimated time:
(Total: 0.00 h)
Description
Use the following strategy for prefetch:
When a read happens on a file, look at the next N blocks the make up the manifest stream and issue prefetch requests for those blocks. These blocks get loaded into the cache so they are ready to go when they are needed.
By looking ahead in the stream rather than just the file, this also works for manifests containing small files which are stored as 1 block per file.
There should be a config knob to control how much data or blocks are prefetched so that sites can experiment with optimal throughput.
This implies the cache behavior needs to support pre-fetch, which means pre-fetched blocks should not push out actively used blocks but should be able to push out less recently used blocks. Plain LRU behavior where a block is promoted each time it is accessed may be sufficient but metrics will be helpful.
- Target version changed from 2022-05-11 sprint to 2022-05-25 sprint
- Target version deleted (
2022-05-25 sprint)
- Target version set to To be groomed
- Release deleted (
60)
- Subject changed from Go FileSystem / FUSE mount supports block caching & prefetch to Go FileSystem / FUSE mount supports block prefetch
- Story points set to 2.0
- Target version changed from To be groomed to To be scheduled
- Description updated (diff)
- Target version changed from To be scheduled to Development 2023-05-10 sprint
- Assigned To set to Tom Clegg
- Target version changed from Development 2023-05-10 sprint to Development 2023-05-24 sprint
- Target version changed from Development 2023-05-24 sprint to Development 2023-06-07
- Target version changed from Development 2023-06-07 to Development 2023-06-21 sprint
- Target version changed from Development 2023-06-21 sprint to To be scheduled
- Related to Story #18342: Keep performance optimization added
- Description updated (diff)
- Description updated (diff)
- Target version changed from To be scheduled to Development 2023-10-25 sprint
Also available in: Atom
PDF