Experiment: Replace ShardedHashMap method insert with debug-checked insert_unique#155550
Experiment: Replace ShardedHashMap method insert with debug-checked insert_unique#155550zetanumbers wants to merge 2 commits intorust-lang:mainfrom
ShardedHashMap method insert with debug-checked insert_unique#155550Conversation
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.
This comment has been minimized.
This comment has been minimized.
Experiment: Replace `ShardedHashMap` method `insert` with debug-checked `insert_unique`
This comment has been minimized.
This comment has been minimized.
|
Finished benchmarking commit (db613ff): comparison URL. Overall result: ✅ improvements - no action neededBenchmarking means the PR may be perf-sensitive. It's automatically marked not fit for rolling up. Overriding is possible but disadvised: it risks changing 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)This perf run didn't have relevant results for this metric. CyclesResults (secondary -2.5%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (primary -0.1%, secondary -0.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 507.073s -> 490.745s (-3.22%) |
Currently every use of
ShardedHashMap::insertchecks that it won't evict an old value due to unique key. I haven't found any issue related to that faulty condition, so I thought of replacing it withShardedHashMap::insert_uniquewhich doesn't check for this condition unlessdebug_assertionsare enabled. This might improve the performance.r? @petrochenkov