pure/benchmarks/tpcc/run.py, branch masterVerified execution runtime unifying state, persistence, and replication.
http://git.yeowoo.org/pure/atom?h=master2026-10-19T00:53:40Z027's 5c: money as i64 minor units shown by .Nd: NUM_TEXT's decimal form takes digits (bits 20-24 as FIXED's), an integer's last N digits written after a point (1234 at two is 12.34, -5 -0.05, 0 0.00; width and zeros after the sign), verification allowing digits on FIXED and DECIMAL alone; unit test: ten rows of formats_and_held (-2^63 at two, 25 digits, a number's whole 1234, its 12.5 a limit); TPC-C's money i64 cents and its rates ten-thousandths (tables, messages, load, the transactions), SQLite's INTEGER columns and int64 bindings alike, the comparison now exact (no 1e-9 tolerance): after 20,000 transactions every row of every table the same (grouped SQLite too) and 3.3.2 holding on both; counts: b45 against b44 BFS without batches +0.09%, the rest within 0.001%; the bank's queries (s44 and s45 in turns, six each) in_credit -0.59%, per_branch -0.34%, ranks -0.20%, the rest within 0.01%, the seven answers the same bytes; 008 (NUM_TEXT's digits, a message row's i64 cells), 027 and 0922026-10-19T00:53:40Zeunhhunecpition205@gmail.com2026-10-19T00:53:40Zurn:sha1:defb2cf06a9b5db9429ca368d8c2af127a5c9c3dRead TPC-C's table dumps from Pure a page at a time2026-09-30T06:22:34Zeunhhunecpition205@gmail.com2026-09-30T06:22:34Zurn:sha1:49c5b0cb8205509ed602d5e6a71ec4edd7b0387f
With four warehouses the order lines answered at once (about 140 MB of
JSON) outgrew pure-serve's 64 MiB budget, and the check stopped with
503; a larger budget would have left the answer's memory in the
resident size measured after.
Checkpoint TPC-C's SQLite each 40 MB of WAL, as tuning on both devices chose2026-09-30T06:18:03Zeunhhunecpition205@gmail.com2026-09-30T06:18:03Zurn:sha1:155b73513017c79dcf235b53f0b4942e80dc2e29
Its default, each 1,000 pages, is 1 MB of WAL with the 1 KiB pages the
SD card favours: grouped commits there went from 203 to 694 a second,
and in RAM a thread's p99 from 1.2 to 0.2 ms (docs/research/106).
Let TPC-C's SQLite commit in groups as pure-serve does, and say what each run costs2026-09-30T06:06:52Zeunhhunecpition205@gmail.com2026-09-30T06:06:52Zurn:sha1:123966fa4a7f65df311960a5d8a42a92ae432408
The terminals hand their writing transactions to one writer, which runs
those waiting in one transaction, each in a savepoint, and commits them
with one sync; reads stay on the terminals' connections, as pure-serve
shows views from the last save. An undone New-Order is rolled back by
its caller now (it rolled back the whole group before, and counted as
failed after the split). Each run reports its CPU a transaction, the
owner thread's share of a core, its memory, and the bytes a transaction
had written, by the process and to the device. SQLite runs with its
database mapped, a 64 MiB cache and savepoint journals in memory unless
told otherwise.
Check TPC-C's consistency from one snapshot a side, and measure TPC-C on RAM and an SD card2026-09-28T10:12:37Zeunhhunecpition205@gmail.com2026-09-28T10:12:37Zurn:sha1:d416c5b2392da7b2dc365e646ab5423292f770ceRun TPC-C on Pure and on SQLite, and compare the states they leave2026-09-28T08:14:10Zeunhhunecpition205@gmail.com2026-09-28T08:14:10Zurn:sha1:a557178f92a0b54fd33b9a7aa14ce66a8c45c060