Uh oh!
There was an error while loading. Please reload this page.
Prehash visibilities in resolver - #143371
Conversation
aaaefd1 to
17c75cbCompare17c75cb to
11751ceComparecjgillot
commented
Jul 4, 2025
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
Prehash visibilities in resolver Based on #143247 r? `@ghost` for perf
bors
commented
Jul 4, 2025
bors
commented
Jul 4, 2025
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
rust-timer
commented
Jul 4, 2025
Finished benchmarking commit (556648c): 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 -1.9%, secondary -2.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary -0.9%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (primary 1.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 461.146s -> 462.46s (0.28%) |
11751ce to
2a49c4cCompare| let visibilities_hash = { | ||
| let mut hasher = StableHasher::new(); | ||
| let mut hcx = self.create_stable_hashing_context(); | ||
| self.visibilities_for_hashing.hash_stable(&mut hcx, &mut hasher); |
There was a problem hiding this comment.
I thought about doing this operation in fn feed_visibility and keeping only the hash in Resolver instead of the whole visibilities_for_hashing table.
Is creating the hashing context a more or less expensive operation than adding a table element?
There was a problem hiding this comment.
Creating a hashing context is very cheap. It's just moving some pointers around. I guess we could keep a StableHasher around, feed it the individual items, and finish into a hash here.
Uh oh!
There was an error while loading. Please reload this page.
This comment was marked as resolved.
This comment was marked as resolved.
2a49c4c to
df4ffb9Comparecjgillot
commented
Aug 3, 2025
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
Prehash visibilities in resolver
This comment has been minimized.
This comment has been minimized.
rust-timer
commented
Aug 4, 2025
Finished benchmarking commit (a723f79): comparison URL. Overall result: ❌✅ regressions and 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 (primary 0.6%, secondary 2.2%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary -2.7%, secondary -2.2%)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: 467.629s -> 467.313s (-0.07%) |
petrochenkov
commented
Aug 6, 2025
@cjgillot |
rustbot
commented
Aug 6, 2025
Reminder, once the PR becomes ready for a review, use |
Based on #143247
r? @ghost for perf