Roundhouse benchmark results — campfire

Run campfire · captured 2026-10-17T10:44:52Z · cceae7c37e05 · 40 cells × 3 runs · 8 endpoints × 5 targets
Artifacts: env.json · per-run.json · summary.json · summary.md · parity.txt
Methodology. AMD Ryzen 5 3600 6-Core Processor, 6c/12t, 3.6 GHz, boost disabled, governor=performance, 63 GB RAM, Ubuntu 24.04.5 LTS. Toolchains pinned via mise. Harness: scripts/bench-campfire — workers=1, c=16, 3×20s runs per cell after 20s warmup; the median of the 3 runs is reported (the run-to-run spread is in the stability section below). Quiet machine throughout. Full hardware, toolchain versions, and the exact invocation are in the environment appendix below.

rails and the emit lanes BOTH serve campfire's message fragments from a cache — Rails from Redis (cached: true), the emitted tree from its own process-local store — so the deployed lanes compare like with like. Until 2026-09-07 the emit had no fragment cache and this page carried a rails-nocache column so the comparison was renderer against renderer rather than emit against Redis; that column is now a diagnostic, requested by name, and is not published here.

The deployed lanes are what each project would run on this box. rails is once-campfire AS ITS OWN DOCKERFILE RUNS IT: Thruster in front of Puma, (processor_count * 0.666).ceil workers x 5 threads from its own config/puma.rb, jemalloc preloaded, resque-pool alongside. ruby is the CRuby emit in the same Puma shape with the same allocator; spinel is the binary with its workers autodetected.

ruby IS A MATCHED-SHAPE RUNTIME COMPARISON, NOT A DEPLOYMENT CLAIM. It runs Rails' worker count so the number is not a core count, but the emitted tree's Action Cable registry and its job queue are both in-process: at more than one worker a broadcast reaches only the subscribers sharing a process with the poster, so campfire could not actually run this shape. Its deployable CRuby shape today is one worker; one process serving every core (Falcon on Ractors, the shape spinel already has) is the planned replacement. spinel needs none of this: one process, green threads, one shared registry — which is why it is the emit lane the WebSocket tier can measure at its full worker count.

ruby-falcon is the SAME emitted tree and config.ru as ruby, served by Falcon (the emit's falcon.rb: forked workers, the same count and allocator, cache hits answered ahead of Falcon's Rack adapter) instead of Puma: the server tobi runs. It isolates what the app server costs. Falcon is added to the emit's bundle by this harness, at the version tobi's lock pins; the emitted Gemfile names only Puma, and the WebSocket phase still runs Puma.

Known omissions, stated rather than discovered: the WebSocket phase's rails lane runs Puma with campfire's worker count and its allocator but WITHOUT Thruster and resque-pool, and no lane terminates TLS.

MEMORY IS THE SERVER PROCESS TREE, and the rails lanes keep part of themselves outside it. Their fragment cache, their Action Cable adapter and Resque's queue all live in a system Redis (~16 MB RSS here) that is nobody's descendant and so is in no lane's number — while the emit lanes hold their equivalent inside the measured process. Throughput is unaffected: the rails lanes pay for every Redis round trip in their req/s. Counted for rails: Thruster, the Puma master and its workers, resque-pool and its workers.

tobi is tobi/campfire-once-ruby-ractor: campfire ported BY HAND to plain Ruby, no Rails, served by Falcon from worker Ractors in one process, with in-process job and cable Ractors. It is the measured answer to "how fast can careful Ruby serve this app", and the target for the emitted ruby lane. It reads the same seeded database. Its deliberate differences from Rails (header-only CSRF, so its pages carry no tokens; part-hashed ETags; fewer cookie writes) are listed in its README.

The CRuby fragment store is PER PROCESS, so the ruby lane holds one cache per worker where spinel holds one for the whole binary.

spinel runs the same Roundhouse-emitted framework as the CRuby ruby cell, but compiled by Spinel behind its thread-per-connection server (a green thread per connection on the runtime's autodetected OS worker count) rather than CRuby + Puma — so the ruby → spinel gap is a runtime swap, not a framework or source change.

1. Throughput across targets

Each endpoint is its own chart. Bars are log-scaled; raw req/sec is shown at the right.

/rooms/1

1,00010,000100,000req/secruby10,922ruby-falcon10,851spinel8,347tobi3,849rails1,852

/rooms/1/messages?before=50

1,00010,000100,000req/secruby-falcon12,091ruby11,964spinel9,884tobi8,027rails1,913

/users/me/sidebar

1,00010,000100,000req/secruby-falcon18,605ruby17,101spinel10,823tobi9,348rails3,112

/searches?q=coffee

1,00010,000100,000req/secruby11,795ruby-falcon10,683spinel9,886tobi3,571rails1,983

/users/:avatar_token/avatar

10,000100,000req/secruby-falcon76,276tobi72,285ruby45,527rails21,782spinel16,365

a stylesheet (/assets/*.css)

10,000100,000req/secruby-falcon87,040tobi77,934spinel53,011ruby47,918rails34,388

/up

1,00010,000100,000req/sectobi55,957spinel37,877ruby-falcon37,393ruby30,782rails4,372

POST /rooms/2/messages

1001,00010,000req/secspinel1,123tobi1,114ruby945ruby-falcon932rails305

2. Lowerer dividend (ruby vs rails)

Same Ruby interpreter, same YJIT, same Puma — the only variable is whether the framework runtime is Rails or Roundhouse-emitted. The multiplier under each pair is the lift from the lowerer pipeline. Bars are log-scaled, so the multiplier, not bar height, is the ratio.

1001,00010,000100,00010,9221,852room5.9×11,9641,913messages6.3×17,1013,112sidebar5.5×11,7951,983search5.9×45,52721,782avatar2.1×47,91834,388css1.4×30,7824,372/up7.0×945305POST3.1×rubyrails

3. Cost economics (req/sec per GB of RSS)

Throughput normalized by memory footprint — req/sec divided by RSS in GB. This reorders the raw throughput charts above: targets with small working sets rise and high-RSS targets fall. Bars are log-scaled. How much the metric matters depends on the deployment shape — most on metered or serverless surfaces, least on bare metal with memory headroom.

/rooms/1

1001,00010,000100,000req/sec/GBspinel86,033ruby21,774ruby-falcon11,792tobi9,831rails1,328

/rooms/1/messages?before=50

1001,00010,000100,000req/sec/GBspinel99,902ruby21,898tobi21,394ruby-falcon12,195rails1,305

/users/me/sidebar

1,00010,000100,0001,000,000req/sec/GBspinel107,350tobi40,475ruby-falcon26,037ruby24,707rails2,002

/searches?q=coffee

1001,00010,000100,000req/sec/GBspinel98,312ruby19,299ruby-falcon10,718tobi5,511rails1,301

/users/:avatar_token/avatar

1,00010,000100,0001,000,000req/sec/GBspinel156,038tobi130,235ruby-falcon105,251ruby36,506rails14,283

a stylesheet (/assets/*.css)

10,000100,0001,000,000req/sec/GBspinel490,911tobi486,659ruby-falcon126,293ruby34,744rails22,571

/up

1,00010,000100,0001,000,000req/sec/GBtobi368,228spinel351,958ruby-falcon54,587ruby44,895rails2,778

POST /rooms/2/messages

1001,00010,000req/sec/GBspinel6,528tobi1,159ruby-falcon812ruby441rails163

4. Memory footprint (PSS)

Max PSS observed across all endpoints, per target, sorted low to high.

PSS, not a sum of RSS: adding RSS across a process tree counts every shared page once per process, which reads high for a clustered lane and changes nothing for a single-process one. PSS divides each shared page among its sharers.

spinel176 MBtobi983 MBruby-falcon1,174 MBrails1,919 MBruby2,189 MB

5. Latency (p50 / p99 at c=16)

Latencies are at c=16 concurrent connections; treat p50 as the median per-connection wait and p99 as the tail. Lanes are ordered by measured median p50 across endpoints, fastest first.

routeruby-falconrubyspineltobirails
p50p99p50p99p50p99p50p99p50p99
/rooms/11.33.31.33.51.64.93.89.08.020.6
/rooms/1/messages?before=501.13.51.23.61.44.21.65.77.740.5
/users/me/sidebar0.82.20.92.71.34.51.64.04.712.6
/searches?q=coffee1.43.51.24.01.34.34.110.67.146.3
/users/:avatar_token/avatar0.20.90.30.90.83.60.23.20.62.5
a stylesheet (/assets/*.css)0.10.80.30.80.21.50.11.90.41.5
/up0.41.30.52.30.31.70.22.33.49.1
POST /rooms/2/messages14.995.915.357.813.479.512.165.844.6227.6

All values in milliseconds. Lower is better.

6. Cold start

Time from exec to a server that answers, and to a signed-in /rooms/1 that comes back 200. Median of 3 boots per lane, all on the shape named in the row. The room page is the number that matters: it contains the first render, and on a fragment-cached lane a restart keeps the Redis its own Procfile runs in a separate process, so this is a warm-cache restart rather than a cold deployment.

targetanswers (ms)room page (ms)
spinel324355
ruby-falcon12101472
tobi13721534
ruby13141597
rails46735562

Milliseconds. Lower is better. A deployed Rails lane boots a proxy, a Puma master and one worker per (processor_count × 0.666).ceil; the binary boots one process.

7. WebSocket connections

Sockets held open, subscribed to a room, then idled and driven: each lane pinned to the same cores, one client, exact delivered/expected frame counts. The idle column is the cost of holding connections that are doing nothing, which is what a chat deployment does most of the time. Read the fan-out latency against the per-room column — one message costs one write per subscriber in its room, so a room of 200 and a room of 50 are different workloads at the same socket count.

targetsocketsper roomconnect stormidle (cores)PSS (MB)fan-out p50 / p99delivering (cores)frames
spinel1,000500.4 s0.00926019 / 51 ms0.0221,500/1,500
ruby1,000501.2 s0.00622432 / 138 ms0.0321,500/1,500
rails1,000502.5 s0.01364638 / 221 ms0.0781,500/1,500

The driver is one thread reading every socket; its longest single reading pass in this run was 58 ms. A fan-out p99 near that number is the client's backlog rather than the server's fan-out.

Memory is PSS where the lane is multi-process, RSS otherwise. Lower is better in every column except frames, which must be exact.

8. What each lane rendered

One authenticated GET per lane per endpoint, captured before any load. Equal tag counts are what makes the throughput numbers above a comparison rather than two measurements.

laneendpointstatustagsbytes
rails/rooms/12003,639400,734
rails/rooms/1/messages?before=502003,375367,595
rails/users/me/sidebar20033037,354
rails/searches?q=coffee2003,544390,527
rails/users/:avatar_token/avatar2007631
railsa stylesheet (/assets/*.css)20001,218
rails/up200273
ruby/rooms/12003,639396,226
ruby/rooms/1/messages?before=502003,375365,275
ruby/users/me/sidebar20033035,295
ruby/searches?q=coffee2003,544386,163
ruby/users/:avatar_token/avatar2007631
rubya stylesheet (/assets/*.css)20001,218
ruby/up200273
ruby-falcon/rooms/12003,639396,226
ruby-falcon/rooms/1/messages?before=502003,375365,275
ruby-falcon/users/me/sidebar20033035,295
ruby-falcon/searches?q=coffee2003,544386,163
ruby-falcon/users/:avatar_token/avatar2007631
ruby-falcona stylesheet (/assets/*.css)20001,218
ruby-falcon/up200273
spinel/rooms/12003,639396,226
spinel/rooms/1/messages?before=502003,375365,275
spinel/users/me/sidebar20033035,295
spinel/searches?q=coffee2003,544386,163
spinel/users/:avatar_token/avatar2007631
spinela stylesheet (/assets/*.css)20001,218
spinel/up200273
tobi/rooms/12003,639395,861
tobi/rooms/1/messages?before=502003,375362,755
tobi/users/me/sidebar20033037,365
tobi/searches?q=coffee2003,544385,127
tobi/users/:avatar_token/avatar2007631
tobia stylesheet (/assets/*.css)20001,218
tobi/up200273

Run-to-run stability

Each cell is timed 3 times and the charts above report the median run. This section reads per-run.json directly to show how far the individual runs strayed from it. Across all 40 cells the median run-to-run coefficient of variation in req/sec is 0.73% — the timed runs of a given cell agree to a fraction of a percent, so the reported medians aren't masking noise.

The 8 cells that vary by more than 3% are concentrated in the lowest-throughput cells, where a small absolute swing is a larger fraction of the rate; in 1 of them the first timed run is the slowest, consistent with residual warmup the fixed 20s warmup doesn't fully absorb:

targetendpointrun 1run 2run 3CV
tobi/up55,95767,03844,25516.7%
tobi{css}77,93459,32587,94115.8%
ruby-falcon/users/me/sidebar19,50218,60516,7336.3%
ruby-falcon{css}87,04079,98892,8756.1%
ruby-falcon/users/{avatar}/avatar76,27669,39778,7135.3%
ruby-falcon/searches?q=coffee10,6839,70310,8224.8%
ruby-falcon/rooms/110,17711,34510,8514.4%
ruby-falcon/up39,66537,39336,6073.4%

req/sec per timed run; CV = standard deviation ÷ mean.

Raw cell data (40 rows)
targetendpointreq/secp50 (ms)p99 (ms)PSS (MB)req/sec/GB
spinel/rooms/18,3471.654.949986,033
spinel/users/me/sidebar10,8231.294.54103107,350
spinel/searches?q=coffee9,8861.344.2710298,312
spinel/rooms/1/messages?before=509,8841.364.2510199,902
spinel/users/{avatar}/avatar16,3650.813.61107156,038
spinel{css}53,0110.241.47110490,911
spinel/up37,8770.331.72110351,958
spinelPOST:/rooms/2/messages1,12313.4079.541766,528
tobi/rooms/13,8493.759.014009,831
tobi/users/me/sidebar9,3481.654.0523640,475
tobi/searches?q=coffee3,5714.0810.586635,511
tobi/rooms/1/messages?before=508,0271.605.7038421,394
tobi/users/{avatar}/avatar72,2850.163.24568130,235
tobi{css}77,9340.141.89163486,659
tobi/up55,9570.212.28155368,228
tobiPOST:/rooms/2/messages1,11412.0765.799831,159
ruby-falcon/rooms/110,8511.323.3094211,792
ruby-falcon/users/me/sidebar18,6050.822.1873126,037
ruby-falcon/searches?q=coffee10,6831.393.541,02010,718
ruby-falcon/rooms/1/messages?before=5012,0911.063.491,01512,195
ruby-falcon/users/{avatar}/avatar76,2760.180.87742105,251
ruby-falcon{css}87,0400.140.79705126,293
ruby-falcon/up37,3930.421.2670154,587
ruby-falconPOST:/rooms/2/messages93214.8695.861,174812
ruby/rooms/110,9221.313.5051321,774
ruby/users/me/sidebar17,1010.862.7170824,707
ruby/searches?q=coffee11,7951.203.9962519,299
ruby/rooms/1/messages?before=5011,9641.183.6455921,898
ruby/users/{avatar}/avatar45,5270.330.861,27736,506
ruby{css}47,9180.310.801,41234,744
ruby/up30,7820.472.3070244,895
rubyPOST:/rooms/2/messages94515.3257.792,189441
rails/rooms/11,8528.0520.631,4271,328
rails/users/me/sidebar3,1124.6812.561,5912,002
rails/searches?q=coffee1,9837.1446.281,5601,301
rails/rooms/1/messages?before=501,9137.7040.541,5001,305
rails/users/{avatar}/avatar21,7820.642.531,56114,283
rails{css}34,3880.441.511,56022,571
rails/up4,3723.379.101,6112,778
railsPOST:/rooms/2/messages30544.60227.601,919163
Environment (captured 2026-10-17T10:44:52Z)

Host

hostnameshowcase.party
OSUbuntu 24.04.5 LTS
kernelLinux showcase.party 6.8.0-147-generic #147-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 24 11:33:16 UTC 2026 x86_64 x86_64 x86_64 GNU/Linux
boardASRock B450 Pro4 R2.0
CPUAMD Ryzen 5 3600 6-Core Processor
topology6 cores / 12 threads
clockgovernor=performance, boost disabled, 3600 MHz max
memory64,228 MB

Application under test

appcampfire
revisionedbc779f4dfc
Rails8.2.0.alpha (e3d5c569d217)
Ruby4.0.5
servedproduction
seed50 users, 5 rooms, 100 messages/room
app server (rails lanes)puma 8.0.2
app server (emit lanes)puma 8.0.1

What each lane actually ran

Recorded at boot, not copied from intent: a lane that asked for jemalloc and did not get one says so here.

railsjemalloc=/usr/lib/x86_64-linux-gnu/libjemalloc.so.2, resque-pool=pid 1177296, thruster=front on :19100 -> puma :20100, workers=campfire's own formula (WEB_CONCURRENCY unset)
rubyjemalloc=/usr/lib/x86_64-linux-gnu/libjemalloc.so.2, workers=8
ruby-falconserver=falcon 0.57.0 via falcon.rb (forked), jemalloc=/usr/lib/x86_64-linux-gnu/libjemalloc.so.2, workers=8
spinelworkers=autodetected
tobiroot=/home/rubys/git/campfire-once-ruby-ractor, revision=353e899, ruby=4.0.5, jemalloc=/usr/lib/x86_64-linux-gnu/libjemalloc.so.2, workers=8 ractors (one process)

Toolchains

cargocargo 1.98.1 (797e8a9bc 2026-08-05)
crystalCrystal 1.20.2 [2482c62c1] (2026-05-15)
curlcurl 8.5.0 (x86_64-pc-linux-gnu) libcurl/8.5.0 OpenSSL/3.0.13 zlib/1.3 brotli/1.1.0 zstd/1.5.5 libidn2/2.3.7 libpsl/0.21.2 (+libidn2/2.3.7) libssh/0.10.6/openssl/zlib nghttp2/1.59.0 librtmp/2.3 OpenLDAP/2.6.10
dotnet10.0.301
gogo version go1.26.4 linux/amd64
jrubyjruby 10.1.1.0 (4.0.0) 2026-07-22 aaa95d57e1 OpenJDK 64-Bit Server VM 25.0.3+9-LTS on 25.0.3+9-LTS +indy +jit [x86_64-linux]
mise2026.5.15 linux-x64 (2026-05-23)
nodev26.3.0
python3Python 3.14.6
redis-serverRedis server v=7.0.15 sha=00000000:0 malloc=jemalloc-5.3.0 bits=64 build=d064f9f48c901a92
rubyruby 4.0.5 (2026-05-20 revision 64336ffd0e) +PRISM [x86_64-linux]
rustcrustc 1.98.1 (48a229cea 2026-09-01)
shardsShards 0.20.0 [b2b98ca] (2025-12-19)
spinelspinel 2026.09.12+10496 (77198b78d) [gcc 13.3.0 (cc)]
sqlite33.45.1 2024-01-30 16:01:20 e876e51a0ed5c5b3126f52e532044363a014bc594cfefa87ffb5b82257ccalt1 (64-bit)
trufflerubytruffleruby 40.0.0 (2026-09-17), like ruby 4.0.2, Oracle GraalVM Native [x86_64-linux]
uvuv 0.11.22 (x86_64-unknown-linux-musl)
wrkwrk debian/4.1.0-4build2 [epoll] Copyright (C) 2012 Will Glozer

Harness

commandscripts/bench-campfire --app /home/rubys/once-campfire --port 19100 --out bench/results/campfire/20261017-111349 rails ruby ruby-falcon spinel tobi
workers1
concurrency16
runs3 × 20s after 20s warmup
wrk threads2
endpoints/rooms/1 /rooms/1/messages?before=50 /users/me/sidebar /searches?q=coffee /users/{avatar}/avatar {css} /up POST:/rooms/2/messages
targetsrails, ruby, ruby-falcon, spinel, tobi

Source

commitcceae7c37e05aba2978071eab74202a4bf913f42
branchmain
subjectMerge pull request #1024 from dai199/ci-spinel-timings

Conditions at start

load average0.52 / 3.86 / 6.23
uptime12:44:53 up 1 day, 23:29, 1 user, load average: 0.52, 3.86, 6.23

Generated 2026-10-17T22:29:31Z from summary.json.