pure/docs/research/096-per-delivery-cpu.md, branch masterVerified execution runtime unifying state, persistence, and replication.
http://git.yeowoo.org/pure/atom?h=master2026-09-29T14:26:56ZSay what a small record costs a link now, beside quinn in the same rounds (096, 100)2026-09-29T14:26:56Zeunhhunecpition205@gmail.com2026-09-29T14:26:56Zurn:sha1:5aa976a63da05874eff34dcb34380fc15f1c9afa
61-byte records: 0.287 us a record against quinn's 0.31 in the same five
rounds (0.93 of it); 096's 1.06-1.12 was against quinn at 0.27, which
moves between 0.27 and 0.32 from day to day. H4 is no longer at the
edge.
Measure a link on paths of loss, reordering and a bottleneck, against quinn (097)2026-09-29T10:49:32Zeunhhunecpition205@gmail.com2026-09-29T10:49:32Zurn:sha1:8140a59205911170e151c95ed5596db7aa0d5ba5
M6 of design 011: with a 50 Mbit/s bottleneck, a link carries 21-41
times quinn's goodput when packets reorder, the same under random loss,
and 1.3-3.5 times with both; its p99 at 50 records a second is the same
or shorter; beside TCP CUBIC it takes 0.48-0.55 of the path, inside the
guardrail. Only on a clean path is it 3-5% below quinn.
Put the links and the crypto they use in link/, a part of their own2026-09-29T06:06:27Zeunhhunecpition205@gmail.com2026-09-29T06:06:27Zurn:sha1:a052b95c8135cdc5f9b91f8efc991cac80fbbe8b
libpure-link.a holds them; pure-serve and the M5 harness link it instead
of naming its source files.
Measure the drains again with the outbox as a list (096)2026-09-29T05:36:47Zeunhhunecpition205@gmail.com2026-09-29T05:36:47Zurn:sha1:0b4a9f7225b5873e606106b8eaf9174b254c0c0f
Between two pure-serve nodes, 16 KiB records drain at 33,600 a second
(23,000 before), the links spending 58 us a record (76), under quinn's 60
while the receiver also stores each one. 1,013 bytes: 406,000 a second
(347,000). Saving sends one by one: 5,000 of 16 KiB in 0.91 s (84.8).
Measure the CPU a record costs a link, against quinn (096)2026-09-29T05:24:43Zeunhhunecpition205@gmail.com2026-09-29T05:24:43Zurn:sha1:c97e4e1a203d13852d5f7cd4a404f88b44f4064f
M5 of design 011. At first a link spent eight times quinn's CPU on a small
record: scans of the backlog, a system call and allocations a record, 19
bytes of framing. After the seven changes before this one, the transport
alone (transport.c; a backlog drained, every record checked) spends per
record 0.30 us for 61 bytes (quinn 0.27: 1.06 to 1.12 times over three
campaigns, at the design's 10 % line), 2.91 us for 1,013 bytes (quinn
3.88) and 45.2 us for 16,013 bytes (quinn 60.9): 25 % less for the larger
ones, and 30 % more records a second. What is left for small records is
per packet: the stream's names and the RECORDS head. quinn's numbers carry
no confirmation of storing and no exactly once.
Between two pure-serve nodes the links spend more per record, woken at
the receiving app's pace. Filling the sender showed the outbox is written
whole at every save, as the numbers heard were (094): the next thing to
change.
run.py gains --transport and --drain; the quinn service reads a drain a
chunk at a time and its client writes 64 KiB at a time.