TraceMachina / TraceMachina/nativelink
Consolidate fast-slow store request
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 244
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 54
Description
If there's multiple requests to the fast-slow store in parallel, they are all serviced at the same time meaning that a slow link to the slow store is made even slower. We should parallelise these requests such that the first request populates the fast store then subsequent requests are served from the instance in the fast store.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the fast-slow store request handling and trace how concurrent requests populate and read the fast store. Reproduce parallel requests if the project provides a relevant test or harness, then verify that one request populates the fast store and subsequent requests use that instance instead of independently accessing the slow store.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100