-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Optimize the compiler on the no-opt bots #7425
Comments
I think we should do a no-opt bootstrap. Once, somewhere. Maybe on a special builder. I agree that the no-opt compiler should not be building the testsuite. It's extremely pessimistic as it runs the many-megabytes deserialize-the-whole-metadata routine once per test through a non-optimized compiler and libstd/libextra. It takes 1.5s-per-test at least to compile (vs. more like 200ms per when optimized, i.e. 7 times faster). Here's a profile of it unoptimized:
Compare with optimized:
|
In concert with this, of course, I still think (have thought for like a year?) that #4572 / changing metadata to store compressed info and ASTs per-item, and load them lazily, is our biggest potential cycle-time win. |
Now that #8450 has landed, I believe that the bots can be configured in this way now, and once cycles times are confirmed down this should be close-able. |
I have now reconfigured the bots this way. |
This is now active. Reopen if you see a reason to. |
These bots take a very long time, surely in large part because they are using an unoptimized compiler. Running the test suite unoptimized seems sufficient for testing Rust without optimizations, and we can do that with a fast compiler.
The text was updated successfully, but these errors were encountered: