Uh oh!
There was an error while loading. Please reload this page.
Remove will_cache_on_disk_for_key_fn - #154591
Conversation
lqd
commented
Mar 30, 2026
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
…<try> Remove `will_cache_on_disk_for_key_fn`
This comment has been minimized.
This comment has been minimized.
rust-timer
commented
Mar 30, 2026
Finished benchmarking commit (0f75a34): comparison URL. Overall result: ❌✅ regressions and improvements - please read the text belowBenchmarking 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. Next Steps: If you can justify the regressions found in this try perf run, please do so in sufficient writing along with @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 (primary 4.0%, secondary 2.2%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 2.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 483.836s -> 484.325s (0.10%) |
Zalathar
commented
Mar 30, 2026
Diff between the two perf runs: https://perf.rust-lang.org/compare.html?start=5a1a969187f4afe604cb916bc5740a09c5062f4b&end=0f75a344ce44035ffe18148c5886f45b63053573&stat=instructions%3Au All of the “significicant” results look like they could be noise, unfortunately. |
Why would you think that? Every |
zetanumbers
commented
Mar 31, 2026
Either way this is also a refactor PR. |
This comment has been minimized.
This comment has been minimized.
9e740ff to
aa17145Comparerustbot
commented
Apr 1, 2026
r? @jieyouxu rustbot has assigned @jieyouxu. Use Why was this reviewer chosen?The reviewer was selected based on:
|
Zalathar
commented
Apr 1, 2026
I don’t quite understand the motivation behind this as a cleanup. It removes a function pointer from the vtable, but replaces it with two booleans in the vtable, which doesn’t strike me as an improvement over the current code. Is there some reason to prefer the approach in this PR? |
jieyouxu
commented
Apr 1, 2026
r? Zalathar (since you're already looking at it) |
rustbot
commented
Apr 1, 2026
|
Pair of bools is smaller than one function pointer. Removes some dynamic dispatch. Less lines of code overall. |
This comment has been minimized.
This comment has been minimized.
Uh oh!
There was an error while loading. Please reload this page.
aa17145 to
239e4ddComparerustbot
commented
May 26, 2026
This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
zetanumbers
commented
May 26, 2026
Since #155080 have been merged this PR might now have a more significant impact on perf. |
cjgillot
commented
May 29, 2026
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
…<try> Remove `will_cache_on_disk_for_key_fn`
This comment has been minimized.
This comment has been minimized.
rust-timer
commented
May 29, 2026
Finished benchmarking commit (aee8937): comparison URL. Overall result: no relevant changes - no action neededBenchmarking means the PR may be perf-sensitive. Consider adding rollup=never if this change is not fit for rolling up. @rustbot label: -S-waiting-on-perf -perf-regression Instruction countThis perf run didn't have relevant results for this metric. Max RSS (memory usage)Results (primary 3.1%, secondary -5.4%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary 5.7%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 511.654s -> 509.773s (-0.37%) |
cjgillot
commented
May 30, 2026
@bors r+ rollup- |
…uwer Rollup of 12 pull requests Successful merges: - #154591 (Remove `will_cache_on_disk_for_key_fn`) - #156672 (Misc improvements to coroutine transform code) - #157027 (HIR ty lowering: Move some things into submodules) - #157051 (Allow two object files for a single CGU in CompiledModule) - #157100 (Some more per owner things) - #153497 (Use `trait_object_dummy_self` more & heavily fix+update related docs) - #155638 (Fix tupled closure signature in `AsyncFn` arg mismatch diagnostic) - #156826 (style: Clarify nullary call and `()` no-break rule applies past max width) - #157004 (Remove unused functions in `value_analysis.rs`) - #157032 (Fixed more &x ->&mut x suggestions) - #157033 (Note irrefutable while let in loop type errors) - #157139 (compiler: `ops::RangeInclusive` → `range::RangeInclusive`) Failed merges: - #156875 (Correct and document semantics of `yield` terminator)
Uh oh!
There was an error while loading. Please reload this page.
View all comments
Refactors
QueryVtablesand removeswill_cache_on_disk_for_key_fnas unnecessary indirection.Based and blocked on #154576.
Expecting perf improvements.