test(blockifier): use the jemalloc allocator for benchmark

starkware-libs · Feb 3, 2025 · 2e96006 · 2e96006
1 parent ac9eee2
commit 2e96006
Show file tree

Hide file tree

Showing 3 changed files with 5 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
@@ -14,6 +14,9 @@ use blockifier::test_utils::transfers_generator::{
 };
 use criterion::{criterion_group, criterion_main, Criterion};
 
+// Note, it might be interesting to run this benchmark with and without the Jemalloc allocator.
+starknet_infra_utils::set_global_allocator!();
+
 pub fn transfers_benchmark(c: &mut Criterion) {
     let transfers_generator_config = TransfersGeneratorConfig {
         recipient_generator_type: RecipientGeneratorType::Random,