A benchmark number is only as credible as the command, configuration, and environment that produced it. Below are the reproducibility notes for each project. Missing or preliminary numbers are labeled, not hidden.
Benchmark classification
Synthetic microbenchmark
No I/O, no network, no persistence. Measures pure computation.
Test-suite benchmark
Runs as part of the test suite. Measures in-process performance.
End-to-end benchmark
Includes HTTP, signing, persistence. Closer to real dispatch.
OVARA
Under Development
Policy evaluation microbenchmarks
In-process testing.B microbenchmarks for policy evaluation.
cd OVARA/runtime/gateway && go test -bench=. ./internal/handlers/
HTTP load test
In the current HTTP load test, approximately 4,010 requests/sec were observed, with approximately 19.76% errors under the tested workload. p50 ~3 ms, p99 ~98 ms.
Network, adapter execution, signing, persistence, approval workflow, external services. These numbers measure pure policy evaluation in process. They are not representative of production dispatch throughput.
Reproduce (benchmark subtests)
cd micro-agent-protocol && npm run build && npm test
No end-to-end agent execution benchmark published. Not independently reproduced.
No reproducible benchmark or build artifact is currently public. The product is live at sidian.dev but its internals cannot be independently inspected.