Update documentation to reflect that debug builds are now supported for profiling

Copilot · ludfjig · simongdavies · commit 3185a0ed017e · 2025-07-31T12:44:13.000+01:00
Co-authored-by: ludfjig &lt;4257730+ludfjig@users.noreply.github.com&gt;
Signed-off-by: Simon Davies &lt;simongdavies@users.noreply.github.com&gt;
diff --git a/docs/benchmarking-hyperlight.md b/docs/benchmarking-hyperlight.md
@@ -74,4 +74,4 @@ Found 1 outliers among 100 measurements (1.00%)
 
 Use `just bench` to run benchmarks with release builds (the only supported configuration). Comparing local benchmark results to github-saved benchmarks doesn't make much sense, since you'd be using different hardware, but you can use `just bench-download os hypervisor [tag] ` to download and extract the GitHub release benchmarks to the correct place folder. You can then run `just bench-ci main` to compare to (and overwrite) the previous release benchmarks. Note that `main` is the name of the baselines stored in GitHub.
 
-**Important**: Benchmarks can only be run with release builds to ensure meaningful performance measurements. Debug builds are not supported for benchmarking.
+**Important**: The `just bench` command uses release builds by default to ensure meaningful performance measurements. For profiling purposes, you can compile benchmarks with debug symbols by running `cargo bench` directly.

Original file line number	Diff line number	Diff line change
`@@ -74,4 +74,4 @@ Found 1 outliers among 100 measurements (1.00%)`
`74`	`74`
`75`	`75`	Use `just bench` to run benchmarks with release builds (the only supported configuration). Comparing local benchmark results to github-saved benchmarks doesn't make much sense, since you'd be using different hardware, but you can use `just bench-download os hypervisor [tag] ` to download and extract the GitHub release benchmarks to the correct place folder. You can then run `just bench-ci main` to compare to (and overwrite) the previous release benchmarks. Note that `main` is the name of the baselines stored in GitHub.
`76`	`76`
`77`		`-Important: Benchmarks can only be run with release builds to ensure meaningful performance measurements. Debug builds are not supported for benchmarking.`
	`77`	+Important: The `just bench` command uses release builds by default to ensure meaningful performance measurements. For profiling purposes, you can compile benchmarks with debug symbols by running `cargo bench` directly.