-
Notifications
You must be signed in to change notification settings - Fork 13.6k
[WIP] resolve: Better caching for unsuccessful crate resolutions #144737
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
base: master
Are you sure you want to change the base?
Conversation
r? @fee1-dead rustbot has assigned @fee1-dead. Use |
@bors2 try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
[WIP] resolve: Better caching for unsuccessful crate resolutions
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (f9cf5ef): comparison URL. Overall result: no relevant changes - no action neededBenchmarking this pull request means it may be perf-sensitive – we'll automatically label it not fit for rolling up. You can override this, but we strongly advise not to, due to possible changes in compiler perf. @bors rollup=never Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)Results (secondary 1.9%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary 4.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (secondary 0.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 467.836s -> 469.081s (0.27%) |
@bors2 try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
[WIP] resolve: Better caching for unsuccessful crate resolutions
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (b757ae7): comparison URL. Overall result: ✅ improvements - no action neededBenchmarking this pull request means it may be perf-sensitive – we'll automatically label it not fit for rolling up. You can override this, but we strongly advise not to, due to possible changes in compiler perf. @bors rollup=never Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (secondary 3.6%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary -0.3%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (secondary 0.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 467.851s -> 468.346s (0.11%) |
resolve: Cleanups and micro-optimizations to extern prelude This is what can be done without changing the structure of `ExternPreludeEntry`, like in rust-lang#144737. See individual commits for details.
resolve: Cleanups and micro-optimizations to extern prelude This is what can be done without changing the structure of `ExternPreludeEntry`, like in rust-lang/rust#144737. See individual commits for details.
Do not call
(maybe_)process_path_extern
again if it already returned false in the past.