<feed xmlns='http://www.w3.org/2005/Atom'>
<title>pure/research/experiments/023-node-reuse/2026-09-30-after-5-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-30T07:54:29Z</updated>
<entry>
<title>Say what snapshots cost the owner, and what reusing their nodes gave (107)</title>
<updated>2026-09-30T07:54:29Z</updated>
<author>
<name>eunhhu</name>
<email>necpition205@gmail.com</email>
</author>
<published>2026-09-30T07:54:29Z</published>
<link rel='alternate' type='text/html' href='http://git.yeowoo.org/pure/commit/?id=9840d27a9e437de32256024a2fd6a3219a239815'/>
<id>urn:sha1:9840d27a9e437de32256024a2fd6a3219a239815</id>
<content type='text'>
Most of it was the allocator: leaves past glibc's thread cache, freed by
whichever thread let the last snapshot go. jemalloc was 11-14% faster
at more memory; reusing the nodes in Pure gave a median +9.4% over six
pairs, 4-8% less CPU a transaction in all six, and 1.97x the state bytes
resident where it was 2.18x. TPC-C in RAM is now 4.0x a tuned SQLite at
W=1 and 3.5x at W=4; finding items is the owner's largest part now.
</content>
</entry>
</feed>
