Skip to content

Notes for future benchmark runs #4565

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Kenny Kerr (kennykerr) merged 1 commit into from
Jun 11, 2026
Merged

Notes for future benchmark runs #4565

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions docs/reactor-vs-csharp.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -366,3 +366,22 @@ investigated and found to be non-issues — Rust handles each correctly by desig

*Last updated: June 2026. Based on C# preview.3 (commit 234364d) and local
Rust crate (commit 1eccc01). All benchmarks measured on the same x64 machine.*

---

## Notes for Future Benchmark Runs

The C# `tests/stress_perf/` directory contains **three** variants:

- **`StressPerf.Reactor`** — base version; rebuilds all 4,800 cells every render
(tree build ~24 ms).
- **`StressPerf.ReactorOptimized`** — caches cells and only rebuilds dirty
indices (tree build ~2 ms). This is the apples-to-apples comparison for Rust,
which uses the same caching strategy by default.
- **`StressPerf.Direct`** — imperative WinUI property-set, no framework overhead.

**Always compare Rust against `ReactorOptimized`, not base `Reactor`.** The
numbers in the tables above were originally collected against the base variant,
which overstated the Rust advantage (e.g. "16× faster reconcile" becomes ~6×
against the optimized variant). The `run_spec034_bench.ps1` script in the C#
repo runs all three variants side-by-side.
Loading