GitHub Actions run
Wall Time
2 days ago 93e63b7 kai/host-value-resource pull_requestUnknown Walltime execution environment detected
Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data. For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.This run is associated to a commit that was force-pushed
It will not be associated with its branch history. Be careful when comparing its performance to other runs.Compare
Suggested base runs: •
19 total
vm_loop_500k
crates/baml_tests/benches/runtime_benchmark.rs21.1 ms
vm_mixed_ops
crates/baml_tests/benches/runtime_benchmark.rs11.9 ms
startup_empty_expression
crates/baml_tests/benches/runtime_benchmark.rs97.9 ms
e2e_100_functions
crates/baml_tests/benches/runtime_benchmark.rs151.3 ms
vm_array_iter_10k
crates/baml_tests/benches/runtime_benchmark.rs5.8 ms
vm_string_concat_5k
crates/baml_tests/benches/runtime_benchmark.rs24.7 ms
compile_to_engine
crates/baml_tests/benches/runtime_benchmark.rs91.6 ms
engine_init_cost
crates/baml_tests/benches/runtime_benchmark.rs3.6 ms
vm_field_access_50k
crates/baml_tests/benches/runtime_benchmark.rs6.8 ms
vm_array_push_50k
crates/baml_tests/benches/runtime_benchmark.rs9.5 ms
e2e_fib_20
crates/baml_tests/benches/runtime_benchmark.rs102.7 ms
e2e_hello_world
crates/baml_tests/benches/runtime_benchmark.rs95.9 ms
vm_nested_loop
crates/baml_tests/benches/runtime_benchmark.rs5.3 ms
vm_closure_call_50k
crates/baml_tests/benches/runtime_benchmark.rs8.7 ms
vm_class_create_50k
crates/baml_tests/benches/runtime_benchmark.rs13.2 ms
e2e_class_and_loop
crates/baml_tests/benches/runtime_benchmark.rs97.3 ms
e2e_arithmetic
crates/baml_tests/benches/runtime_benchmark.rs94.5 ms
vm_call_chain_100_x_5k
crates/baml_tests/benches/runtime_benchmark.rs35.1 ms
vm_fib_20
crates/baml_tests/benches/runtime_benchmark.rs5.4 ms