<feed xmlns='http://www.w3.org/2005/Atom'>
<title>pure/research/experiments/021-memory/2026-09-30-window-linux-aarch64.jsonl, branch master</title>
<subtitle>Verified execution runtime unifying state, persistence, and replication.
</subtitle>
<id>http://git.yeowoo.org/pure/atom?h=master</id>
<link rel='self' href='http://git.yeowoo.org/pure/atom?h=master'/>
<link rel='alternate' type='text/html' href='http://git.yeowoo.org/pure/'/>
<updated>2026-09-30T02:42:36Z</updated>
<entry>
<title>Say what the windows and checkpoints cost (013 steps 2 and 3, 104)</title>
<updated>2026-09-30T02:42:36Z</updated>
<author>
<name>eunhhu</name>
<email>necpition205@gmail.com</email>
</author>
<published>2026-09-30T02:42:36Z</published>
<link rel='alternate' type='text/html' href='http://git.yeowoo.org/pure/commit/?id=6b3b1c64328fb6b4932dfb67fd05486182657673'/>
<id>urn:sha1:6b3b1c64328fb6b4932dfb67fd05486182657673</id>
<content type='text'>
013's second step is in (d9e0b68): each transport holds a window of its
output's sends. 104 measures it with the receivers down: once the window
is full a node grows by the outbox alone, 219 and 218 B a send over the
link and HTTP (399 and 534 B before).

The third step is a measurement. A checkpoint holds one list's snapshot
while it writes the image, so what it adds is what the app changed
meanwhile: nothing visible on tmpfs or for a list that fits the card's
fast writes; on the SD card, a 22.4 MB list written for about 8 s while
1,400 items a second were set left +3.0 and +4.4 MiB. The highest
resident memory was twice the state bytes, inside 013's bound (the state
and one snapshot) and its stop criterion (3x).

021's run.py takes --items, --stores (a directory on the device to
measure) and --label, and reports the peak (VmHWM).
</content>
</entry>
</feed>
