improve `proxy_mode` (e.g. rustc wrapper) startup time?
Open
Nobody has claimed this yet.
enhancement
help wanted
performance
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 22h 40m
- Merged PRs (30d)
- 46
Description
time ~/.rustup/toolchains/master/bin/rustc >& /dev/null
0,040 total
time ~/.cargo/bin/rustc >& /dev/null
0,272 total
That's almost 7x slower.
I wonder if there is some something we can do to get these numbers a bit closer?
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
Reproduce the comparison between ~/.rustup/toolchains/master/bin/rustc and ~/.cargo/bin/rustc using the provided time commands, then trace rustup's proxy_mode startup path. Measure the wrapper overhead and identify where the extra startup time is introduced. Done means bringing the proxy-mode timing materially closer to the direct rustc timing without changing its behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- performance, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100