-
Notifications
You must be signed in to change notification settings - Fork 13k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bootstrap: Memoize the LLVM rebuild hash to avoid very slow x check
#118352
Conversation
(rustbot has picked a reviewer for you, use r? to override) |
This PR changes how LLVM is built. Consider updating src/bootstrap/download-ci-llvm-stamp. |
This is an alternative to #118351. It's very much intended as a quick-fix to solve the immediate issue of no-op check builds taking way too long (~30 sec instead of ~2 sec). I'm open to fixing this in better ways, but I think it's worth at least working around this as soon as possible, so that people's dev environments are functional again. (I assume this is one of those issues that stems from git being way faster on Linux than on other platforms.) |
@bors r+ |
☀️ Test successful - checks-actions |
Finished benchmarking commit (b29a1e0): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 674.949s -> 675.168s (0.03%) |
Recently I've encountered a massive regression in the performance of re-running
x check
after making no changes.It used to take around 2 seconds, and now it takes 20-30 seconds. That's quite a hassle when r-a runs it every time I save.
After some poking around, what I've found is that each individual call to
generate_smart_stamp_hash
takes only a modestly long time (around 0.5 sec), but it gets called dozens of times duringx check
, and that seems to be what's adding up to 20-30 seconds.https://rust-lang.zulipchat.com/#narrow/stream/326414-t-infra.2Fbootstrap/topic/Massive.20regression.20in.20no-op.20.60x.20check.60
cc @onur-ozkan