chore: add criterion benchmark for evm build

[shane-moore]

Changes

• This PR closes Add benchmark for Evm build #2308 by adding a benchmark to measures the how long the EVM build takes to initialization instructions via evm.replay()

Note:

• the build_mainnet step was left out of the benchmark as to focus on time spent to initialize instructions. Let me know if the intention was to include the build_mainnet into the benchmark as well, and I'll happily add it 🤙

[codspeed-hq]

CodSpeed Performance Report

Merging #2319 will not alter performance

_{Comparing shane-moore:chore/benchmark-evm-build (e537c96) with main (89f273a)}

Summary

✅ 8 untouched benchmarks
🆕 1 new benchmarks

Benchmarks breakdown

	Benchmark	BASE	HEAD	Change
🆕	evm-build	N/A	8.3 µs	N/A

[shane-moore]

hi @rakita, this PR is ready for review whenever you get a chance

[rakita]

Suggested change

	let _ = evm.replay().unwrap();
	let _ = Context::mainnet().build_mainnet();

Buildering of EVM should be here, not a replay.

[shane-moore]

gotcha! updated to

revm/bins/revme/src/cmd/bench/evm_build.rs

Lines 4 to 9 in e537c96

	pub fn run(criterion: &mut Criterion) {
	criterion.bench_function("evm-build", |b| {
	b.iter(|| {
	let _ = Context::mainnet().build_mainnet();
	});
	});

[rakita]

Suggested change

	BenchName::EvmBuild => "evm_build",
	BenchName::EvmBuild => "evm-build",

For outside names using dash is better.

[shane-moore]

great point @rakita, updated to:

revm/bins/revme/src/cmd/bench.rs

Line 33 in e537c96

BenchName::EvmBuild => "evm-build",

agreed that cargo bench --package revme -- evm-build does look cleaner