-
Notifications
You must be signed in to change notification settings - Fork 1
Benchmarks
mkuch edited this page Jul 17, 2026
·
6 revisions
RayoMD benchmark claims are dated, scoped, and reproducible. Hardware, storage, fonts, compiler, tool versions, and document shape all affect results.
-
RayoMD tester.md Warm Benchmark 2026-07-17 - sub-10 ms warm
tester.mdoptimization record - Markdown-to-PDF Speed Comparison 2026-07-13 - current three-tool Windows comparison
- RayoMD 2.2.0 Optimization Audit 2026-07-13 - profiling, concurrency, LTO/PGO, and release evidence
- Reversible PDF Feature Benchmark 2026-07-13 - embedding, recovery, limits, workflows, and memory
- Markdown-to-PDF Speed Comparison 2026-07-11 - earlier three-tool comparison
- RayoMD vs Pandoc 2026-06-18 - focused local Windows export comparison
- Commercial Benchmark Campaign 2026-06-06 - large synthetic runs, batching, and serve mode
- Optimization Progress - accepted and rejected native-path experiments
- Optimization Research Notes - research sources and follow-up candidates
- Issue 20 Completion Matrix - archived reversible-PDF completion evidence
- Warm
--benchtiming measures repeated in-process PDF byte generation. - Export and batch timing includes process and file I/O.
- Synthetic inputs are not a representative customer corpus.
- Linux/WSL storage matters: native ext4 can be dramatically faster than
/mnt/*for many small files. - Native RayoMD implements a narrower feature set than Pandoc and browser-based renderers. Speed comparisons are not claims of feature or visual equivalence.
Use Performance Watcher for current before/after measurements. Compact
version records remain in
docs/benchmarks/releases
because scripts consume them and they belong to source history.