Repository navigation
bench(linux): record thermally verified paired warm IPC v3 corpus - #53
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (84)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe pull request adds warm-cache paired Bun/Rust IPC-RTT benchmark results for 6-byte and 1 KiB payloads. It records 20 paired rounds, warmup metadata, bootstrap statistics, raw artifact bindings, thermal conditions, and diagnostic-only publication status. ChangesWarm-cache IPC benchmark
Priority: ⬇️ Low Estimated code review effort: 3 (Moderate) | ~25 minutes Change: Other 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Provenance
Benchmark recipe:
ed134e360506cf1c5a9abdc817e9e31ff42af53bKeld:
0ea0780bb574ad242e9f1105fa4af5842872bad3Evidence commit:
882079970cb85accdf16297df493ff8dc6d6d507Campaign
Thermal boundary:
p99 results
Small, 6 B:
Representative, 1,024 B:
Claim boundary
The v3 documents remain diagnostic-only for:
PRODUCT_CLIENT_VS_LIBRARY_FLOOR_DIAGNOSTIC.The Bun arm is the shipping TypeScript product-client slice; the Rust arm is the direct library floor. This is not pure Bun runtime overhead and not end-to-end application latency.
Fresh and warm are separate campaigns. Their central values must not be subtracted into a causal cache-state speedup/regression claim.
Bloat/integrity
Validation
git diff --check: passLinear: KEL-90.
Summary by CodeRabbit