test(blockifier): use the jemalloc allocator for benchmark

starkware-libs · Feb 3, 2025 · ee04cc7 · ee04cc7
1 parent 962ea8c
commit ee04cc7
Show file tree

Hide file tree

Showing 3 changed files with 8 additions and 0 deletions.
diff --git a/Cargo.lock b/Cargo.lock
diff --git a/crates/blockifier/Cargo.toml b/crates/blockifier/Cargo.toml
@@ -83,6 +83,7 @@ rstest.workspace = true
 rstest_reuse.workspace = true
 starknet_api = { path = "../starknet_api", features = ["testing"] }
 test-case.workspace = true
+tikv-jemallocator.workspace = true
 
 [build-dependencies]
 starknet_infra_utils.workspace = true

diff --git a/crates/blockifier/bench/blockifier_bench.rs b/crates/blockifier/bench/blockifier_bench.rs
@@ -13,6 +13,12 @@ use blockifier::test_utils::transfers_generator::{
     TransfersGeneratorConfig,
 };
 use criterion::{criterion_group, criterion_main, Criterion};
+use starknet_infra_utils::set_global_allocator;
+
+// TODO(Arni): Consider how to run this benchmark both with and without setting the allocator. Maybe
+// hide this macro call under a feature, and run this benchmark regularly or with
+// `cargo bench --bench blockifier_bench --feature=specified_allocator`
+set_global_allocator!();
 
 pub fn transfers_benchmark(c: &mut Criterion) {
     let transfers_generator_config = TransfersGeneratorConfig {