<feed xmlns='http://www.w3.org/2005/Atom'>
<title>pure/research/experiments/013-parallel-syncs/probe.c, 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-27T12:57:51Z</updated>
<entry>
<title>Measure whether sharding owners by key would add writes (084)</title>
<updated>2026-09-27T12:57:51Z</updated>
<author>
<name>eunhhu</name>
<email>necpition205@gmail.com</email>
</author>
<published>2026-09-27T12:57:51Z</published>
<link rel='alternate' type='text/html' href='http://git.yeowoo.org/pure/commit/?id=5e90a99dfdcc0a16f52213370cda29779571e36c'/>
<id>urn:sha1:5e90a99dfdcc0a16f52213370cda29779571e36c</id>
<content type='text'>
It would not, on this device. One file's syncs or four at once, the SD card
completes the same 510-690 commits per second, the latency growing with the
number of files. The scoreboard app with two owners, each with a store of
its own, took 23% fewer durable posts than one owner (median 16,230 against
20,974 a second) with 2-3x the p99: syncs queue, and each carries half the
events. One owner's group commit stays; cores serve reads, and writes grow
by making the sync itself cheaper.

</content>
</entry>
</feed>
