writeonce/docs
shoney.arickathil 929b2802c4 add wo-rt-c: C runtime prototype, phases A-F shipped
prototypes/wo-rt-c — single-file C reference of the writeonce runtime
layer, zero deps beyond libc + kernel uapi: thread-per-core io_uring
event loops (raw syscalls, no liburing), SO_REUSEPORT listeners, one
mlock'd mmap arena sharded by address, WAL dual-write with group commit
(HTTP ack only after the fsync CQE), boot-time snapshot + WAL replay
recovery, and a bench harness with a Go net/http comparison server.

Measured on 20 cores: 908k reads/s p99 154us and 643k fsync-acked
commits/s p99 177us on 8 shards, vs Go net/http 495k/355k (no
durability) on 20 cores. Crash-under-load testing found and fixed an
ack-before-fsync race and an fd-reuse ABA hazard in commit-ack parking.

docs/plan/exploration/c-runtime — the phased plan (00, exit evidence
per phase), the one-address architecture trace (01), and the
single-binary end-goal contract (02). justfile carries the demo and
bench recipes; .gitignore covers binaries and data dirs.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-06-12 23:05:13 +02:00
..
examples single thread event loop runtime 2026-05-04 23:16:10 +02:00
future-scope Pivot to the .wo language runtime: design docs, phase plans 2026-04-21 02:48:45 +02:00
plan add wo-rt-c: C runtime prototype, phases A-F shipped 2026-06-12 23:05:13 +02:00
runtime Pivot to the .wo language runtime: design docs, phase plans 2026-04-21 02:48:45 +02:00
01-problem.md begin 2026-04-05 00:45:02 +02:00
02-recovery.md explore postgres code base 2026-05-05 00:26:49 +02:00
03-data.md begin 2026-04-05 00:45:02 +02:00
04-ui.md begin 2026-04-05 00:45:02 +02:00
05-datalayer.md begin 2026-04-05 00:45:02 +02:00
06-markdown-render.md begin 2026-04-05 00:45:02 +02:00
07-ssl.md begin 2026-04-05 00:45:02 +02:00