Flower / Field notesReactive database · Raft · TypeScript

Goblin Pizza Express / Benchmark report

The rush-hour report.

Goblins bake. Drones deliver. Raft keeps the books.
Scheduled ovens, leased deliveries, and reactive shop totals under load.

Passed

2026-09-25 05:44:47 UTC

66.28 s total wall time · 0 unexpected failures

Customer goodput

6,953.2 / s

70% reads · 30% mutations among successful customer calls.

All-call latency

All-call latency: 431,716 calls; p50 2.06 ms, p99 180 ms, max 736 ms. Log axis from 0.0301 ms to 816 ms.

p50 2.06 ms · p99 180 ms. All load-phase logical calls, including worker traffic, replays, discovery, and retries.

Orders delivered

96 / 96

247 pizzas · 1,729 copper in delivery revenue.

Quorum recovery

559.7 ms

First recorded crash to a serving quorum; restart catch-up is tracked separately.

Replica-local customer previews: replication lag is allowed. The selected pizza.shop.local method uses coherent locally applied snapshots without a quorum fence. Data, code, and aliases may lag without a bound; requests across replicas can return decreasing revisions. Replica-local is the benchmark default; choose --read-consistency fresh to measure quorum-fenced previews. Mutations and the final pizza.world audit retain fresh semantics.

The customer's view

Successful work, precisely counted.

One Raft group
Successful customer mix
70% reads / 30% mutations
Successful customer calls
418,083
Failed customer calls
0
Measured load duration
60.13 s
Load worker completions excluded
1,056
Load replay completions excluded
12,577
Customer goodput uses actual successful primary customer calls and the measured load duration.
Load measurementSuccessful completionsGoodput / sSuccessful customer share
Primary customer reads292,4894,864.470%
Primary customer mutations125,5942,088.830%
All primary customer calls418,0836,953.2100%
All logical calls, including workers and replays431,7167,179.9Includes non-customer traffic
Raw successful HTTP responses431,7167,179.9Includes retries and non-customer traffic

Counting definition: successful pizza.shop.local, pizza.order, and pizza.tip logical calls per measured load second. Transport retries count once when their customer call succeeds. Explicit .replay probes, worker claims and deliveries, polling, setup, audit, and every failed call contribute zero customer goodput. Actual successful read/mutation shares appear above.

The run verdict covers correctness and completion of any requested CPU profile. Customer goodput is an average over the recorded load phase; individual intervals can differ.

The rush, second by second

How the run unfolded

61 recorded time samples

Observed completion rate

Each point summarizes the interval since the previous sample.

Interval throughput over timeSuccessful HTTP responses and completed logical calls per second in each sampling interval. Dashed vertical lines mark recorded leader crashes. 61 samples over 60.28 s since load start. HTTP responses: first 18.5, last 0.0 events / s. Logical calls: first 18.5, last 0.0 events / s.00s2,73115s5,46230s8,19345s10,92460sLeader crash at 30.03 s after load startCrashHTTP responsesLogical calls
HTTP responsesLogical callsevents / s · elapsed load time

Cumulative HTTP tail latency

p95 of attempts since load began; not an interval percentile.

Cumulative HTTP p95 over timeThe latency p95 is cumulative from load start through each sample, including drain. It is not a moving-window or interval percentile. 61 samples over 60.28 s since load start. Cumulative p95: first 278.6, last 137.4 ms.00s7015s13930s20945s27960sLeader crash at 30.03 s after load startCrashCumulative p95
Cumulative p95ms · elapsed load time

Orders placed and delivered

Acknowledgements observed by the benchmark driver.

Acknowledged orders and deliveries over timeCumulative acknowledged order and delivery counts. Their gap shows business work still waiting for completion. 61 samples over 60.28 s since load start. Orders: first 0.0, last 96.0 orders. Deliveries: first 7.0, last 96.0 orders.00s2415s4830s7245s9660sLeader crash at 30.03 s after load startCrashOrdersDeliveries
OrdersDeliveriesorders · elapsed load time

Driver resident memory

Samples include the driver's runtime and retained workload records.

Driver resident memory over timeBenchmark driver resident memory sampled over elapsed load time. 61 samples over 60.28 s since load start. Driver RSS: first 301.6, last 416.0 MiB.00s10415s20830s31245s41660sLeader crash at 30.03 s after load startCrashDriver RSS
Driver RSSMiB · elapsed load time

Lines connect observed samples; no measurements are interpolated into the underlying data. Throughput is an interval rate, while p95 is cumulative. The driver and database share a machine. Any crash marker is positioned relative to the start of measured load.

Recorded time samples
Retries and HTTP failures are counts for each interval. Cumulative p95 covers all attempts since load began.
ElapsedPhaseHTTP attempts / sHTTP success / sLogical complete / sRetriesHTTP failuresCumulative p95OrdersDeliveriesDriver MiB
1.08 sload18.518.518.500278.6 ms07301.6
2.16 sload9,208.09,208.09,208.000226.0 ms9616316.7
3.16 sload5,661.05,661.05,661.000200.6 ms9628318.5
4.16 sload6,058.06,058.06,058.000185.2 ms9644321.6
5.16 sload7,065.67,065.67,065.600176.3 ms9661324.8
6.20 sload5,978.55,978.55,978.500172.8 ms9677326.5
7.20 sload7,049.97,049.97,049.900171.1 ms9691327.5
8.21 sload7,168.67,168.67,168.600164.4 ms9694329.1
9.21 sload6,353.56,353.56,353.500161.2 ms9696330.9
10.22 sload6,754.56,754.56,754.500159.6 ms9696332.6
11.22 sload7,146.27,146.27,146.200154.9 ms9696334.2
12.22 sload6,600.16,600.16,600.100154.9 ms9696335.7
13.23 sload6,721.86,721.86,721.800153.3 ms9696337.4
14.23 sload7,205.37,205.37,205.300150.3 ms9696341.1
15.23 sload8,194.58,194.58,194.500148.8 ms9696345.3
16.23 sload7,804.27,804.27,804.200145.9 ms9696346.9
17.22 sload6,698.76,698.76,698.700144.5 ms9696348.3
18.23 sload6,825.46,825.46,825.400144.5 ms9696350.0
19.23 sload7,154.17,154.17,154.100143.0 ms9696351.6
20.23 sload7,184.37,184.37,184.300143.0 ms9696353.2
21.23 sload6,980.76,980.76,980.700143.0 ms9696354.8
22.23 sload6,067.16,067.16,067.100144.5 ms9696356.4
23.23 sload5,325.95,325.95,325.900147.4 ms9696358.3
24.23 sload5,041.05,041.05,041.000148.8 ms9696359.5
25.23 sload6,312.26,312.26,312.200148.8 ms9696361.2
26.23 sload6,965.96,965.96,965.900148.8 ms9696362.8
27.23 sload6,151.16,151.16,151.100147.4 ms9696364.3
28.23 sload7,424.27,424.27,424.200147.4 ms9696366.1
29.23 sload5,933.85,933.85,933.800148.8 ms9696368.0
30.23 sload6,550.26,034.16,034.1256516148.8 ms9696369.9
31.23 sload5,660.24,332.34,332.31,5891,329147.4 ms9696373.8
32.23 sload8,363.88,268.98,268.99595147.4 ms9696375.9
33.23 sload4,173.24,132.24,132.24141147.4 ms9696377.9
34.23 sload10,924.210,924.210,924.200145.9 ms9696379.5
35.23 sload8,282.78,282.78,282.700144.5 ms9696374.4
36.23 sload9,769.29,769.29,769.200143.0 ms9696376.0
37.23 sload5,047.45,047.45,047.400145.9 ms9696377.7
38.23 sload4,791.34,791.34,791.300148.8 ms9696379.3
39.23 sload7,293.27,293.27,293.200147.4 ms9696381.0
40.24 sload7,591.27,591.27,591.200147.4 ms9696382.7
41.24 sload7,923.67,923.67,923.600145.9 ms9696384.3
42.24 sload9,769.09,769.09,769.000144.5 ms9696386.0
43.24 sload9,900.79,900.79,900.700143.0 ms9696387.8
44.24 sload8,778.38,778.38,778.300143.0 ms9696389.4
45.24 sload8,968.58,968.58,968.500141.6 ms9696391.0
46.24 sload8,776.28,776.28,776.200141.6 ms9696392.7
47.24 sload8,850.48,850.48,850.400140.2 ms9696394.3
48.24 sload6,275.56,275.56,275.500140.2 ms9696395.8
49.24 sload5,912.05,912.05,912.000141.6 ms9696397.5
50.24 sload5,987.35,987.35,987.300141.6 ms9696399.0
51.24 sload6,727.36,727.36,727.300141.6 ms9696400.6
52.24 sload7,378.57,378.57,378.500141.6 ms9696402.2
53.24 sload6,824.26,824.26,824.200141.6 ms9696403.8
54.24 sload7,884.47,884.47,884.400141.6 ms9696405.4
55.25 sload7,456.97,456.97,456.900140.2 ms9696407.0
56.25 sload9,646.49,646.49,646.400140.2 ms9696408.6
57.25 sload9,617.09,617.09,617.000138.8 ms9696410.3
58.25 sload9,423.49,423.49,423.400138.8 ms9696411.8
59.25 sload10,060.410,060.410,060.400137.4 ms9696413.5
60.25 sdrain8,715.58,715.58,715.500137.4 ms9696416.0
60.28 sdrain0.00.00.000137.4 ms9696416.0

The shape of the rush

Throughput & response time

Closed-loop workload

Successful work by phase

Actual measured phase durations appear below the bars.

Successful throughput by phaseSuccessful HTTP responses and completed logical calls per second for each phase. Setup: HTTP responses 1.2 events / s, Logical calls 1.2 events / s. Warmup: HTTP responses 10,719.5 events / s, Logical calls 10,719.5 events / s. Load: HTTP responses 7,179.9 events / s, Logical calls 7,179.9 events / s. Drain: HTTP responses 6.7 events / s, Logical calls 6.7 events / s. Audit: HTTP responses 43.0 events / s, Logical calls 43.0 events / s02,6805,3608,04010,720Setup · HTTP responses: 1.2 events / sSetup · Logical calls: 1.2 events / sSetup4.27 sWarmup · HTTP responses: 10,719.5 events / sWarmup · Logical calls: 10,719.5 events / sWarmup1.01 sLoad · HTTP responses: 7,179.9 events / sLoad · Logical calls: 7,179.9 events / sLoad60.13 sDrain · HTTP responses: 6.7 events / sDrain · Logical calls: 6.7 events / sDrain0.15 sAudit · HTTP responses: 43.0 events / sAudit · Logical calls: 43.0 events / sAudit0.02 s
HTTP responsesLogical callsevents / s · linear scale

Logical latency by phase

Retry and discovery time remain visible in the tails.

Logical calls by the phase they started in. One log axis from 0.0301 ms to 816 ms; each line marks p99.
PopulationCallsLatency
Setup5Setup: 5 calls; p50 284 ms, p99 403 ms, max 403 ms. Log axis from 0.0301 ms to 816 ms.p99 403 ms
Warmup10,855Warmup: 10,855 calls; p50 22 ms, p99 53.4 ms, max 81.9 ms. Log axis from 0.0301 ms to 816 ms.p99 53.4 ms
Load431,716Load: 431,716 calls; p50 2.06 ms, p99 180 ms, max 736 ms. Log axis from 0.0301 ms to 816 ms.p99 180 ms
Drain1Drain: 1 call; p50 6.93 ms, p99 6.93 ms, max 6.93 ms. Log axis from 0.0301 ms to 816 ms.p99 6.93 ms
Audit10Audit: 10 calls; p50 1.64 ms, p99 8.66 ms, max 8.66 ms. Log axis from 0.0301 ms to 816 ms.p99 8.66 ms

A successful HTTP response is not necessarily a new business mutation: receipt replays count as responses, and queries also count. Phase percentiles cover successful and failed attempts or calls. Warmup uses reads and is not comparable to the mixed load phase.

Every call accounted for

Requests, retries & methods

Load details expanded below
Load HTTP attempts
433,697
Load HTTP successes
431,716
Load HTTP failures
1,981
Load retry attempts
1,981
Load duplicate responses
12,693
Load logical failures
0

Network retries belong to the same logical call. Deliberate deduplication probes appear separately as .replay calls. Expected stale-lease failures can appear in these measurements without failing the benchmark.

Setup4.27 s · 5 HTTP attempts
Successful HTTP / s
1.2
Completed logical / s
1.2
HTTP failures
0
Logical failures
0

HTTP error categories: None recorded

Setup HTTP attempts. Latency histograms share one log axis from 3.39 ms to 559 ms; each line marks p99.
HTTP methodAttemptsSucceededFailedRetriesDuplicatesSuccess / sLatency
deploy110000.2deploy HTTP attempts: 1 call; p50 282 ms, p99 282 ms, max 282 ms. Log axis from 3.39 ms to 559 ms.p99 282 ms
pizza.setup110000.2pizza.setup HTTP attempts: 1 call; p50 31.8 ms, p99 31.8 ms, max 31.8 ms. Log axis from 3.39 ms to 559 ms.p99 31.8 ms
pizza.shop330000.7pizza.shop HTTP attempts: 3 calls; p50 399 ms, p99 403 ms, max 403 ms. Log axis from 3.39 ms to 559 ms.p99 403 ms
Logical calls, including explicit replays
One logical call includes discovery, retries, and backoff. Explicit replay checks are separate .replay calls. Latency histograms share one log axis from 3.39 ms to 559 ms.
Logical methodCallsCompletedFailedDuplicatesComplete / sLatency
deploy11000.2deploy logical calls: 1 call; p50 282 ms, p99 282 ms, max 282 ms. Log axis from 3.39 ms to 559 ms.p99 282 ms
pizza.setup11000.2pizza.setup logical calls: 1 call; p50 31.8 ms, p99 31.8 ms, max 31.8 ms. Log axis from 3.39 ms to 559 ms.p99 31.8 ms
pizza.shop33000.7pizza.shop logical calls: 3 calls; p50 399 ms, p99 403 ms, max 403 ms. Log axis from 3.39 ms to 559 ms.p99 403 ms
Warmup1.01 s · 10,855 HTTP attempts
Successful HTTP / s
10,719.5
Completed logical / s
10,719.5
HTTP failures
0
Logical failures
0

HTTP error categories: None recorded

Warmup HTTP attempts. Latency histograms share one log axis from 2.13 ms to 105 ms; each line marks p99.
HTTP methodAttemptsSucceededFailedRetriesDuplicatesSuccess / sLatency
pizza.shop.local10,85510,85500010,719.5pizza.shop.local HTTP attempts: 10,855 calls; p50 22 ms, p99 53.4 ms, max 81.8 ms. Log axis from 2.13 ms to 105 ms; 0.037% of calls fall outside it.p99 53.4 ms
Logical calls, including explicit replays
One logical call includes discovery, retries, and backoff. Explicit replay checks are separate .replay calls. Latency histograms share one log axis from 2.13 ms to 105 ms.
Logical methodCallsCompletedFailedDuplicatesComplete / sLatency
pizza.shop.local10,85510,8550010,719.5pizza.shop.local logical calls: 10,855 calls; p50 22 ms, p99 53.4 ms, max 81.9 ms. Log axis from 2.13 ms to 105 ms; 0.037% of calls fall outside it.p99 53.4 ms
Load60.13 s · 433,697 HTTP attempts
Successful HTTP / s
7,179.9
Completed logical / s
7,179.9
HTTP failures
1,981
Logical failures
0

HTTP error categories: HTTP_503 2 · network 1,979

Load HTTP attempts. Latency histograms share one log axis from 0.0359 ms to 570 ms; each line marks p99.
HTTP methodAttemptsSucceededFailedRetriesDuplicatesSuccess / sLatency
pizza.claim96496044016.0pizza.claim HTTP attempts: 964 calls; p50 92.3 ms, p99 215 ms, max 299 ms. Log axis from 0.0359 ms to 570 ms.p99 215 ms
pizza.deliver10910900131.8pizza.deliver HTTP attempts: 109 calls; p50 116 ms, p99 268 ms, max 277 ms. Log axis from 0.0359 ms to 570 ms.p99 268 ms
pizza.order1031030071.7pizza.order HTTP attempts: 103 calls; p50 143 ms, p99 254 ms, max 254 ms. Log axis from 0.0359 ms to 570 ms.p99 254 ms
pizza.shop.local292,674292,48918518504,864.4pizza.shop.local HTTP attempts: 292,674 calls; p50 1.03 ms, p99 12.6 ms, max 657 ms. Log axis from 0.0359 ms to 570 ms; 0.040% of calls fall outside it.p99 12.6 ms
pizza.tip139,847138,0551,7921,79212,6732,296.0pizza.tip HTTP attempts: 139,847 calls; p50 104 ms, p99 207 ms, max 326 ms. Log axis from 0.0359 ms to 570 ms.p99 207 ms
Logical calls, including explicit replays
One logical call includes discovery, retries, and backoff. Explicit replay checks are separate .replay calls. Latency histograms share one log axis from 0.0329 ms to 1.17 s.
Logical methodCallsCompletedFailedDuplicatesComplete / sLatency
pizza.claim9609600016.0pizza.claim logical calls: 960 calls; p50 93.2 ms, p99 257 ms, max 680 ms. Log axis from 0.0329 ms to 1.17 s.p99 257 ms
pizza.deliver9696001.6pizza.deliver logical calls: 96 calls; p50 118 ms, p99 277 ms, max 277 ms. Log axis from 0.0329 ms to 1.17 s.p99 277 ms
pizza.deliver.replay13130130.2pizza.deliver.replay logical calls: 13 calls; p50 87.8 ms, p99 145 ms, max 145 ms. Log axis from 0.0329 ms to 1.17 s.p99 145 ms
pizza.order9696001.6pizza.order logical calls: 96 calls; p50 133 ms, p99 254 ms, max 254 ms. Log axis from 0.0329 ms to 1.17 s.p99 254 ms
pizza.order.replay77070.1pizza.order.replay logical calls: 7 calls; p50 143 ms, p99 185 ms, max 185 ms. Log axis from 0.0329 ms to 1.17 s.p99 185 ms
pizza.shop.local292,489292,489004,864.4pizza.shop.local logical calls: 292,489 calls; p50 1.03 ms, p99 12.6 ms, max 657 ms. Log axis from 0.0329 ms to 1.17 s.p99 12.6 ms
pizza.tip125,498125,49801162,087.2pizza.tip logical calls: 125,498 calls; p50 105 ms, p99 217 ms, max 736 ms. Log axis from 0.0329 ms to 1.17 s.p99 217 ms
pizza.tip.replay12,55712,557012,557208.8pizza.tip.replay logical calls: 12,557 calls; p50 98 ms, p99 203 ms, max 736 ms. Log axis from 0.0329 ms to 1.17 s.p99 203 ms
Drain0.15 s · 1 HTTP attempts
Successful HTTP / s
6.7
Completed logical / s
6.7
HTTP failures
0
Logical failures
0

HTTP error categories: None recorded

Drain HTTP attempts. Latency histograms share one log axis from 1.92 ms to 25.6 ms; each line marks p99.
HTTP methodAttemptsSucceededFailedRetriesDuplicatesSuccess / sLatency
pizza.world110006.7pizza.world HTTP attempts: 1 call; p50 6.85 ms, p99 6.85 ms, max 6.85 ms. Log axis from 1.92 ms to 25.6 ms.p99 6.85 ms
Logical calls, including explicit replays
One logical call includes discovery, retries, and backoff. Explicit replay checks are separate .replay calls. Latency histograms share one log axis from 1.92 ms to 25.6 ms.
Logical methodCallsCompletedFailedDuplicatesComplete / sLatency
pizza.world11006.7pizza.world logical calls: 1 call; p50 6.93 ms, p99 6.93 ms, max 6.93 ms. Log axis from 1.92 ms to 25.6 ms.p99 6.93 ms
Audit0.02 s · 10 HTTP attempts
Successful HTTP / s
43.0
Completed logical / s
43.0
HTTP failures
9
Logical failures
9

HTTP error categories: HTTP_422 9

Audit HTTP attempts. Latency histograms share one log axis from 0.959 ms to 12.7 ms; each line marks p99.
HTTP methodAttemptsSucceededFailedRetriesDuplicatesSuccess / sLatency
pizza.deliver909000.0pizza.deliver HTTP attempts: 9 calls; p50 1.59 ms, p99 1.76 ms, max 1.76 ms. Log axis from 0.959 ms to 12.7 ms.p99 1.76 ms
pizza.world1100043.0pizza.world HTTP attempts: 1 call; p50 8.62 ms, p99 8.62 ms, max 8.62 ms. Log axis from 0.959 ms to 12.7 ms.p99 8.62 ms
Logical calls, including explicit replays
One logical call includes discovery, retries, and backoff. Explicit replay checks are separate .replay calls. Latency histograms share one log axis from 0.959 ms to 12.7 ms.
Logical methodCallsCompletedFailedDuplicatesComplete / sLatency
pizza.deliver90900.0pizza.deliver logical calls: 9 calls; p50 1.64 ms, p99 1.81 ms, max 1.81 ms. Log axis from 0.959 ms to 12.7 ms.p99 1.81 ms
pizza.world110043.0pizza.world logical calls: 1 call; p50 8.66 ms, p99 8.66 ms, max 8.66 ms. Log axis from 0.959 ms to 12.7 ms.p99 8.66 ms

From the oven to the doorstep

Business completion latency

Load and drain combined

Oven lateness96 samples

Oven lateness: 96 samples; p50 54.5 ms, p99 221 ms, max 221 ms. Log axis from 3.46 ms to 255 ms.5 ms10 ms20 ms50 ms100 ms200 ms3.79 ms–4.14 ms: 1.0% of samples (1)22.7 ms–24.8 ms: 2.1% of samples (2)24.8 ms–27.1 ms: 17.7% of samples (17)27.1 ms–29.7 ms: 9.4% of samples (9)46.5 ms–50.8 ms: 1.0% of samples (1)50.8 ms–55.6 ms: 21.9% of samples (21)104 ms–114 ms: 1.0% of samples (1)149 ms–163 ms: 35.4% of samples (34)213 ms–233 ms: 10.4% of samples (10)p50 54.5 msp99 221 ms

Order to door96 samples

Order to door: 96 samples; p50 4.34 s, p99 8.37 s, max 8.37 s. Log axis from 643 ms to 9.43 s.1 s2 s5 s682 ms–724 ms: 3.1% of samples (3)724 ms–769 ms: 1.0% of samples (1)816 ms–866 ms: 3.1% of samples (3)919 ms–976 ms: 1.0% of samples (1)1.4 s–1.48 s: 3.1% of samples (3)1.48 s–1.57 s: 1.0% of samples (1)1.77 s–1.88 s: 2.1% of samples (2)1.88 s–2 s: 2.1% of samples (2)2.25 s–2.39 s: 4.2% of samples (4)2.54 s–2.69 s: 4.2% of samples (4)2.69 s–2.86 s: 2.1% of samples (2)2.86 s–3.03 s: 3.1% of samples (3)3.03 s–3.22 s: 2.1% of samples (2)3.22 s–3.42 s: 2.1% of samples (2)3.42 s–3.63 s: 7.3% of samples (7)3.63 s–3.85 s: 3.1% of samples (3)3.85 s–4.09 s: 1.0% of samples (1)4.09 s–4.34 s: 4.2% of samples (4)4.34 s–4.61 s: 7.3% of samples (7)4.61 s–4.89 s: 6.3% of samples (6)4.89 s–5.19 s: 4.2% of samples (4)5.19 s–5.51 s: 4.2% of samples (4)5.51 s–5.85 s: 8.3% of samples (8)5.85 s–6.21 s: 4.2% of samples (4)6.21 s–6.59 s: 8.3% of samples (8)6.59 s–7 s: 2.1% of samples (2)7 s–7.43 s: 3.1% of samples (3)7.89 s–8.37 s: 1.0% of samples (1)8.37 s–8.89 s: 1.0% of samples (1)p50 4.34 sp99 8.37 s
Show as tables
Oven lateness: 96 samples, 0 invalid, 0 beyond 24 hours
LatencySamplesShareCumulative
3.79 ms–4.14 ms11.04%1.04%
22.7 ms–24.8 ms22.08%3.13%
24.8 ms–27.1 ms1717.71%20.83%
27.1 ms–29.7 ms99.38%30.21%
46.5 ms–50.8 ms11.04%31.25%
50.8 ms–55.6 ms2121.88%53.13%
104 ms–114 ms11.04%54.17%
149 ms–163 ms3435.42%89.58%
213 ms–233 ms1010.42%100%
Order to door: 96 samples, 0 invalid, 0 beyond 24 hours
LatencySamplesShareCumulative
682 ms–724 ms33.13%3.13%
724 ms–769 ms11.04%4.17%
816 ms–866 ms33.13%7.29%
919 ms–976 ms11.04%8.33%
1.4 s–1.48 s33.13%11.46%
1.48 s–1.57 s11.04%12.50%
1.77 s–1.88 s22.08%14.58%
1.88 s–2 s22.08%16.67%
2.25 s–2.39 s44.17%20.83%
2.54 s–2.69 s44.17%25.00%
2.69 s–2.86 s22.08%27.08%
2.86 s–3.03 s33.13%30.21%
3.03 s–3.22 s22.08%32.29%
3.22 s–3.42 s22.08%34.38%
3.42 s–3.63 s77.29%41.67%
3.63 s–3.85 s33.13%44.79%
3.85 s–4.09 s11.04%45.83%
4.09 s–4.34 s44.17%50.00%
4.34 s–4.61 s77.29%57.29%
4.61 s–4.89 s66.25%63.54%
4.89 s–5.19 s44.17%67.71%
5.19 s–5.51 s44.17%71.88%
5.51 s–5.85 s88.33%80.21%
5.85 s–6.21 s44.17%84.38%
6.21 s–6.59 s88.33%92.71%
6.59 s–7 s22.08%94.79%
7 s–7.43 s33.13%97.92%
7.89 s–8.37 s11.04%98.96%
8.37 s–8.89 s11.04%100%
Configured oven delay
250.0 ms
Configured lease duration
2,000.0 ms
Delivered orders / s, including drain
1.6
Retained order cap
96

Oven lateness measures how far execution runs past the requested deadline. It does not include the configured baking delay. Order-to-door latency includes the entire lifecycle. Each log time axis spans its population's p0.1 to p99.9; the tables list every bin.

The goblin ledger

Business invariants & tenant rankings

Audit passed
96 of 96 acknowledged orders delivered. The independent audit found no invariant violations.
Scores are revenue plus tips, in integer copper coins. Rows follow each tenant’s independently derived leaderboard; this is not a global ranking.
Tenant / kitchenOrdersPizzas deliveredStock leftRevenueTipsScore
tenant-2 / The Crispy Cauldron · store-03795299665106,451107,116
tenant-2 / Dough or Die · store-335389356,4256,460
tenant-2 / The Sizzling Slime · store-2310384706,3636,433
tenant-2 / Mushroom Mayhem · store-125389356,3506,385
tenant-3 / The Goblin's Slice · store-046119275833106,948107,781
tenant-3 / The Crispy Cauldron · store-213391216,4376,458
tenant-3 / Dragon Breath Delivery · store-125389356,3956,430
tenant-3 / Mushroom Mayhem · store-325389356,2966,331

A dragon ate the leader

Failover, leases & replay safety

3 Raft replicas · one group

Leader crash 1

2026-09-25 05:45:22 UTC
Crash recovery: leader 1 killed; serving quorum after 559.7 ms; restarted node caught up after 2,718.3 ms. Both durations are measured from the crash.Leader 1 killed0.0 msQuorum serving; leader 2559.7 msRestarted node caught up2,718.3 ms
Recovery observations, all measured from the leader crash
Recovery milestoneTime since crash
Candidate observed in metrics—
Leader observed in metrics528.3 ms
Quorum read probe completed559.7 ms
Leader discovery returned559.7 ms
Restarted node caught up2,718.3 ms

Metrics observations follow polling and are not exact internal transition times. A brief candidate state can be missed; observing a leader alone does not establish a serving quorum. Missing milestones were not recorded or did not finish. Recovery and catch-up durations share the crash as time zero.

Receipt replays verified
12,577
Stale drones rejected by audit
9
Leases claimed
105
Empty claims
855
Deliberately abandoned leases
9
Reclaimed jobs
9
Lease losses during workload
0
Orders issued
96
End-of-run replica observations, collected separately. These are replicas of one Raft group, not independent shards.
ReplicaObserved roleObserved leaderLast applied index
Node 1Follower21,148
Node 2Leader21,148
Node 3Follower21,148

The cost of a pizza rush

Resource footprint

Co-located processes

Sampled peak resident memory

Sampled peak resident memory by processPeak observed resident memory per server and benchmark driver. Samples can miss brief peaks; per-process peaks need not occur together. Node 1: Peak sampled RSS 320.0 MiB. Node 2: Peak sampled RSS 310.5 MiB. Node 3: Peak sampled RSS 285.2 MiB. Driver: Peak sampled RSS 416.0 MiB0104208312416Node 1 · Peak sampled RSS: 320.0 MiBNode 1Node 2 · Peak sampled RSS: 310.5 MiBNode 2Node 3 · Peak sampled RSS: 285.2 MiBNode 3Driver · Peak sampled RSS: 416.0 MiBDriver
Peak sampled RSSMiB · linear scale
Cluster disk footprint
134.96 MiB
Node controller sampled load cores
0.05
Node controller CPU, user / entire run
3,738.3 ms
Node controller CPU, system / entire run
559.6 ms
Node controller event-loop delay p99
50.5 ms
Node controller sampled peak RSS
416.0 MiB
Rust customer driver peak RSS
20.6 MiB
Rust customer driver sampled load cores
0.13

RSS is sampled, not an allocation total. Server CPU, when available, uses cumulative process CPU deltas over sampled load intervals; one core means one CPU-second per elapsed second. Restart and phase-boundary gaps are excluded. Older reports did not measure it. The load generator and all nodes share the same host, so these numbers include local resource contention and do not establish multi-host network performance.

CPU observations during load; node coverage can differ. Includes all process threads.
ServerMean CPU coresCPU time coveredWall time coveredIntervals
10.4023,110.0 ms57,246.7 ms57
20.4325,570.0 ms59,247.5 ms59
30.148,080.0 ms59,247.5 ms59

Make the result reproducible

Workload, host & measurement limits

Report schema 1

Workload configuration

Application transport
HTTP/2 · h2c prior knowledge
Admin and discovery transport
HTTP/1.1
Query routing
Round-robin across live replicas
Customer read policy
Replica-local · lag allowed
Bundle initialization
static
Customer loops / drone loops
256 / 4
Requested load / warmup
60.0 s / 1.0 s
Maximum drain
60.0 s
Tenants / stores per tenant
2 / 4
Hot stores per tenant
1
Hot-set mixture weight
80%
Duplicate / abandonment probability
10% / 10%
Worker polling interval
150.0 ms
Request timeout / retry budget
2,000.0 ms / 15,000.0 ms
Workload seed
42:group-1
Crash injection requested
Yes

Execution environment

JavaScript engine
quickjs
Runtime settings
{"TOKIO_WORKER_THREADS":"2","FLOWER_WRITER_BATCH_MODE":"adaptive","FLOWER_WRITER_QUEUE_CAPACITY":"1024","FLOWER_QUERY_WORKERS":"16","FLOWER_PREPARATION_WORKERS":"16","FLOWER_WRITER_PREPARATION_WORKERS":"1","FLOWER_WRITER_WINDOW_MS":"50","FLOWER_WRITER_BATCH_MS":"50"}
CPU
Apple M5 Pro
Logical CPUs
18
Operating system
darwin 27.2.0
Architecture
arm64
Node.js controller
v26.10.0
Customer driver
rust
Customer driver SHA-256
b3ce2a3e598826cd14bf319d0f65cee7a47b3b3822b7474bd1b987d2d5808e7f
Co-located database nodes
3
Binary SHA-256
a53ad2ae79f74da0f9ddf5d79a2450beebd0efb0e7e00f0cdfcd70929f34d35d
Binary size
45,119,536 bytes
Started
2026-09-25 05:44:47 UTC
Finished
2026-09-25 05:45:53 UTC
Preserved database files
Not retained

How to read these numbers

Complete run options and bundle identity
{
  "options": {
    "offeredRate": 0,
    "groups": 1,
    "tenants": 2,
    "duration": 60,
    "warmup": 1,
    "drain": 60,
    "concurrency": 256,
    "workers": 4,
    "shops": 4,
    "hotShops": 1,
    "hotProbability": 0.8,
    "maxOrders": 96,
    "bakeMs": 250,
    "leaseMs": 2000,
    "duplicateRate": 0.1,
    "abandonRate": 0.1,
    "pollMs": 150,
    "requestTimeoutMs": 2000,
    "retryBudgetMs": 15000,
    "nodes": 3,
    "seed": "42:group-1",
    "initialization": "static",
    "queryRouting": "replicas",
    "readConsistency": "replica-local",
    "driver": "rust",
    "driverBinary": "/Users/pcarrier/src/flower/target/release/flower-bench-driver",
    "binary": "/Users/pcarrier/src/flower/target/release/flower",
    "json": "/Users/pcarrier/src/flower/bench/results/latest-groups/group-1.json",
    "html": "/Users/pcarrier/src/flower/bench/results/latest-groups/group-1.html",
    "baseline": null,
    "cpuProfile": null,
    "chaos": true,
    "http2": true,
    "keepData": false,
    "help": false,
    "runId": "d4e5cf27-0a78-41ed-850e-68ccdca97756",
    "tenantIds": [
      "tenant-2",
      "tenant-3"
    ]
  },
  "runtime": {
    "engine": "quickjs",
    "settings": {
      "TOKIO_WORKER_THREADS": "2",
      "FLOWER_WRITER_BATCH_MODE": "adaptive",
      "FLOWER_WRITER_QUEUE_CAPACITY": "1024",
      "FLOWER_QUERY_WORKERS": "16",
      "FLOWER_PREPARATION_WORKERS": "16",
      "FLOWER_WRITER_PREPARATION_WORKERS": "1",
      "FLOWER_WRITER_WINDOW_MS": "50",
      "FLOWER_WRITER_BATCH_MS": "50"
    }
  },
  "queryRouting": {
    "mode": "replicas",
    "consistency": "replica-local",
    "auditConsistency": "fresh",
    "nodes": [
      {
        "id": 1,
        "url": "http://127.0.0.1:62804",
        "attempts": 98016,
        "completed": 97831,
        "failures": 185
      },
      {
        "id": 2,
        "url": "http://127.0.0.1:62818",
        "attempts": 102759,
        "completed": 102759,
        "failures": 0
      },
      {
        "id": 3,
        "url": "http://127.0.0.1:62821",
        "attempts": 102759,
        "completed": 102759,
        "failures": 0
      }
    ]
  },
  "binary": {
    "path": "/Users/pcarrier/src/flower/target/release/flower",
    "sha256": "a53ad2ae79f74da0f9ddf5d79a2450beebd0efb0e7e00f0cdfcd70929f34d35d",
    "bytes": 45119536,
    "modifiedAt": "2026-09-25T05:16:03.202Z"
  },
  "driver": {
    "kind": "rust",
    "orchestration": "node",
    "binary": {
      "path": "/Users/pcarrier/src/flower/target/release/flower-bench-driver",
      "sha256": "b3ce2a3e598826cd14bf319d0f65cee7a47b3b3822b7474bd1b987d2d5808e7f",
      "bytes": 7136160,
      "modifiedAt": "2026-09-25T05:15:43.417Z"
    },
    "warmupRequests": 3
  },
  "bundleHash": "d3b5c3e6fa9e51548200e79cde504fc967a5d7100a49af12a43f27560721ad64"
}

When the oven smokes

Diagnostics

0 unexpected failures

No unexpected failure details were recorded. Intentional stale-lease rejections and retried HTTP failures are reported in their own counters.