<feed xmlns='http://www.w3.org/2005/Atom'>
<title>pure/research/experiments/022-tpcc-grouped/2026-09-30-tune-ram-defaults-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-30T06:56:49Z</updated>
<entry>
<title>Say what TPC-C costs when SQLite commits in groups too, and with four warehouses (106)</title>
<updated>2026-09-30T06:56:49Z</updated>
<author>
<name>eunhhu</name>
<email>necpition205@gmail.com</email>
</author>
<published>2026-09-30T06:56:49Z</published>
<link rel='alternate' type='text/html' href='http://git.yeowoo.org/pure/commit/?id=0a57c3ad03df6da7eb0a72059bd85c4d716dbb8a'/>
<id>urn:sha1:0a57c3ad03df6da7eb0a72059bd85c4d716dbb8a</id>
<content type='text'>
SQLite tuned first, by the criteria committed before (and, beyond them,
checkpoints each 40 MB of WAL, in its favour). On the SD card Pure stays
4.2-10.8x ahead at equal terminals, SQLite writing 8-18x the bytes a
transaction; in RAM 3.2-3.5x. All tables equal at W=1 and W=4, and
every run consistent. In RAM the one owner is the limit (0.94 of a core
at W=4, no gain from 16 to 64 terminals), a third of its busy time
copying nodes the snapshots share; checkpoints and memory are within
their criteria.
</content>
</entry>
</feed>
