-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
[tentative] Revert "Convert ShardedHashMap
to use hashbrown::HashTable
"
#138708
base: master
Are you sure you want to change the base?
Conversation
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
[tentative] Revert "Convert `ShardedHashMap` to use `hashbrown::HashTable`" rust-lang#138414 (comment) r? fmease
This comment has been minimized.
This comment has been minimized.
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
[tentative] Revert "Convert `ShardedHashMap` to use `hashbrown::HashTable`" rust-lang#138414 (comment) r? fmease
The job Click to see the possible cause of the failure (guessed by this bot)
|
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
@bors try (Made the job explicit in the PR description to run the full build and test suite) |
[tentative] Revert "Convert `ShardedHashMap` to use `hashbrown::HashTable`" rust-lang#138414 (comment) r? fmease try-job: dist-x86_64-linux
Wait, why? The first try build failure concerned the patch before the force push, the subsequent try build success concerned the patch after it. Everything was just fine? |
Ah, sorry, I thought it failed during a merge but succeeded in a try build. |
Same for me, we maybe should show the sha being tested in the result log to disambiguate the results when multiple builds are in flight. |
Maybe we can try using (But I'm also surprised that the switch to |
The perf results are not so bad to be "must revert" in my opinion either. |
The result look neutral except for doc builds, which is a bit odd as the query system is quite hot for check builds. The code also looks equivalent to the old code, ignoring inlining. |
☀️ Try build successful - checks-actions |
I definitely want to avoid reverting two PRs and bringing an FCP-closed feature back to life. I've just quickly spun up this PR to possibly start some perf experiments starting with a clean revert (which might've been overkill I admit).
That would be awesome! |
Finished benchmarking commit (f93dc40): comparison URL. Overall result: ❌✅ regressions and improvements - please read the text belowBenchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never Instruction countThis is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.
Max RSS (memory usage)Results (primary -0.8%, secondary -2.5%)This 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.
CyclesResults (secondary 1.0%)This 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.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 776.901s -> 780.89s (0.51%) |
Try using std's hashbrown copy Just testing if this affects performance. It may relate to rust-lang#138708, rust-lang#137701 and rust-lang#115747.
#138414 (comment)
r? fmease
try-job: dist-x86_64-linux