Enable criterion flamegraphs

[krishnangovindraj]

Usage and product changes

Re-enables flame graphs on the criterion storage benchmarks.

To execute a benchmark, we can either run it via Cargo:

cargo bench --package storage --bench bench_mvcc_storage --profile-time=5

or via Bazel:

bazel test --compilation_mode=opt //storage/benches:bench_mvcc_storage --test_arg=--bench --test_arg=--profile-time=5

Note that this currently does not finish successfull on ARM64 Macs because of a SIGBUS in libunwind.

Implementation

Re-enables flame graphs on the criterion storage benchmarks and updates dependencies to include require pprof library.

[vaticle-bot]

PR Review Checklist

Do not edit the content of this comment. The PR reviewer should simply update this comment by ticking each review item below, as they get completed.

---

Trivial Change

• [ ] This change is trivial and does not require a code or architecture review.

Code

• [ ] Packages, classes, and methods have a single domain of responsibility.
• [ ] Packages, classes, and methods are grouped into cohesive and consistent domain model.
• [ ] The code is canonical and the minimum required to achieve the goal.
• [ ] Modules, libraries, and APIs are easy to use, robust (foolproof and not errorprone), and tested.
• [ ] Logic and naming has clear narrative that communicates the accurate intent and responsibility of each module (e.g. method, class, etc.).
• [ ] The code is algorithmically efficient and scalable for the whole application.

Architecture

• [ ] Any required refactoring is completed, and the architecture does not introduce technical debt incidentally.
• [ ] Any required build and release automations are updated and/or implemented.
• [ ] Any new components follows a consistent style with respect to the pre-existing codebase.
• [ ] The architecture intuitively reflects the application domain, and is easy to understand.
• [ ] The architecture has a well-defined hierarchy of encapsulated components.
• [ ] The architecture is extensible and scalable.