MVCC benchmarks

[serathius]

Benchmark for #22332

[kubernetes-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: serathius

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [serathius]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.72%. Comparing base (03e41f2) to head (3bd2952).

Additional details and impacted files

see 22 files with indirect coverage changes

@@            Coverage Diff             @@
##             main   #22333      +/-   ##
==========================================
- Coverage   69.73%   69.72%   -0.01%     
==========================================
  Files         448      448              
  Lines       38159    38159              
==========================================
- Hits        26609    26607       -2     
- Misses      10117    10122       +5     
+ Partials     1433     1430       -3     

---

Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 03e41f2...3bd2952. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[kubernetes-prow]

@serathius: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-etcd-verify	3bd2952	link	true	/test pull-etcd-verify
pull-etcd-grpcproxy-e2e-arm64	3bd2952	link	true	/test pull-etcd-grpcproxy-e2e-arm64
pull-etcd-e2e-386	3bd2952	link	true	/test pull-etcd-e2e-386

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.