Files
RedBear-OS/local/recipes/shells/brush/source/docs/how-to/run-benchmarks.md
T
vasilito 25fb843c40 brush: vendor the source tree (un-ignore) to complete the local fork
The prior commit switched the recipe to `[source] path = "source"`, but
.gitignore:77 still listed `local/recipes/shells/brush/source` (a leftover from
when brush was a transient upstream git fetch), so the vendored tree was not
tracked — a fresh clone would have no brush source and the build would fail.
Drop that ignore line and commit the vendored working tree (reubeno/brush @
897b373e, with the Redox port patches pre-applied). brush is now a durable
local fork like the other path=source recipes.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-26 23:34:31 +09:00

668 B

How to run benchmarks

The project provides cargo xtask commands for running benchmarks:

# Run benchmarks
cargo xtask analyze bench

# Run benchmarks and save output to a file
cargo xtask analyze bench --output benchmarks.txt

Manual Approach (Alternate)

To run performance benchmarks:

cargo bench --workspace --benches

Collecting flamegraphs

To collect flamegraphs from performance benchmarks (running for 10 seconds):

cargo bench --workspace --benches -- --profile-time 10

The flamegraphs will be created as .svg files and placed under target/criterion/<benchmark_name>/profile.