[do not merge] Benchmark unconditional incr. comp. fingerprint verification

[michaelwoerister]

Let's see how big the slowdown is compared to the current state of things.

cc #85783

r? @ghost

[michaelwoerister]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

@rustbot label: +S-waiting-on-perf

[bors]

⌛ Trying commit 563792d with merge 8eb79e7ec566e6f8e30472424c90de8287d53c3e...

[bors]

☀️ Try build successful - checks-actions
Build commit: 8eb79e7ec566e6f8e30472424c90de8287d53c3e (8eb79e7ec566e6f8e30472424c90de8287d53c3e)

[rust-timer]

Queued 8eb79e7ec566e6f8e30472424c90de8287d53c3e with parent ce0d64e, future comparison URL.

[rust-timer]

Finished benchmarking try commit (8eb79e7ec566e6f8e30472424c90de8287d53c3e): comparison url.

Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. Please note that if the perf results are neutral, you should likely undo the rollup=never given below by specifying rollup- to bors.

Importantly, though, if the results of this run are non-neutral do not roll this PR up -- it will mask other regressions or improvements in the roll up.

@bors rollup=never
@rustbot label: +S-waiting-on-review -S-waiting-on-perf

[Mark-Simulacrum]

death checking seems to at least be a common piece of self-profile results showing regressions across the top few benchmarks -- I wonder if there's some local optimizations that can be made (e.g., making queries no_hash or something, I don't remember the names of the attributes too well) to avoid some of the cost here.

[michaelwoerister]

I'll use the benchmark results collected here for proposing a design meeting about increasing test coverage. Closing the PR.