-
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
[DO NOT MERGE] Try indexmap
with its own RawTable
#129965
Conversation
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
[DO NOT MERGE] Try `indexmap` with its own `RawTable` I want to see whether there's any noticeable performance difference in `rustc` if `indexmap` embeds its own copy of `hashbrown::raw::RawTable<usize>`, specialized for its own use. The generic parameters are removed, as well as a lot of unused code, and some of the raw API is further tweaked for dealing with always-copyable `usize` data. * Full `indexmap` comparison: indexmap-rs/indexmap@master...cuviper:raw * Changes after the initial import: indexmap-rs/indexmap@cfb8d04...cuviper:raw r? ghost
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.
Finished benchmarking commit (d3ed2e8): comparison URL. Overall result: ✅ improvements - no action neededBenchmarking 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. @bors rollup=never Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)Results (primary -2.7%, secondary -0.7%)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 -4.4%)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 sizeResults (secondary -0.1%)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.
Bootstrap: 751.345s -> 750.983s (-0.05%) |
Huh, that is kind of surprising that it came back so neutral. Expanding "non-relevant results" looks like it did maybe make a slight gain overall, but nothing to write home about. It doesn't seem to justify the effort to maintain a separate |
I want to see whether there's any noticeable performance difference in
rustc
ifindexmap
embeds its own copy ofhashbrown::raw::RawTable<usize>
, specialized for its own use. The generic parameters are removed, as well as a lot of unused code, and some of the raw API is further tweaked for dealing with always-copyableusize
data.indexmap
comparison: indexmap-rs/indexmap@master...cuviper:rawr? ghost