rust-lang / rust-lang/rustc-perf
cannot re-deploy server in the middle of benchmarking
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 733
- Forks
- 189
- Avg merge
- 10h 52m
- Merged PRs (30d)
- 43
Description
Currently, if we've added a new postgres migration, then the server will stall on startup until the collection server finishes benchmarking the current transaction.
The correct fix for this is to probably remove the 2.5 hour long transaction that we currently have going on the backend.
To do so we need to support re-starting a pre-existing benchmark. The newly added "progress" table might be a good way of doing that.
Contributor guide
No contributing guide indexed for this repository
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
Start by tracing the collection server's benchmarking flow and the newly added progress table. Define how a pre-existing benchmark can be restarted so a new Postgres migration does not wait for the current long-running transaction; done means the server can redeploy while benchmarking continues safely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgres, rust
- Domain
- backend, databases, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100