Skip to content
PathfinderThe Burst of Creativity
Live snapshot · 4m ago
Board 01 · activity & throughput

Fleet Performance

The client fleet exploring self-avoiding random walks: the work over time, who did it, how efficiently, and whether more workers would help.

Compiled 2026-11-01 13:53
4m ago · refresh 300s
2 clients could not be reached at build time — their performance.log was unreadable. They are flagged, not dropped, in §V.

3 of 5 client machines are reporting, running 30 worker processes between them. Together they have explored 663.35B walks and kept 12K as interesting — about 1 in 55.4M — over 41,078.7 compute-hours. The fleet is presently turning at 828.18M paths an hour. What follows is its portrait: the work accumulated over time, how each machine ranks, how efficiently each worker runs, and whether adding more workers would still buy more throughput.

Paths explored
663.35B
663,348,605,181 across the fleet
Interesting
12K
0.0000% hit rate
Throughput
828.18M /hr
peak 39.17M/hr per worker
Clients
3 / 5
2 unreachable
Compute time
1711d 15h
summed worker runtime
Paths collected
62.5K
saved on the server
I

The work over time

cumulative paths since the first checkpoint

Paths explored across the whole fleet, accumulated from the earliest logged checkpoint to the latest.

0200B400B600B800B1TJul 5, 06:01Sep 1, 15:58Nov 1, 13:52
Fig. 1. Cumulative paths against wall-clock time. The blue curve is the fleet total; switch to By client for one ink curve per machine, each labelled at its head.
II

Paths explored by client

total output per machine
0100B200B300B400B500BPathfinder BPathfinder B: 293,351,432,996 paths293.35BPathfinder CPathfinder C: 292,492,172,185 paths292.49BA New BeginningA New Beginning: 77,505,000,000 paths77.51B
III

Worker efficiency

throughput per worker — the fair race
Fleet throughput
828.18M /hr
Per worker (avg)
27.61M /hr
Projected / day
19.88B
Median time / path
206.0 µs
010M20M30M40M50MA New BeginningA New Beginning: 38,492,746 paths/hr per worker38.49MPathfinder BPathfinder B: 17,641,476 paths/hr per worker17.64MPathfinder CPathfinder C: 13,305,887 paths/hr per worker13.31M
Table 1. Per-client efficiency, derived from performance.log alone. Stability is 1 − the throughput coefficient of variation.
ClientWorkersThroughput /hrPer worker /hr Time / pathHit rateStabilityProj. / day
A New Beginning 16 615,883,937 38,492,746 94.5 µs 0.0000% 98% 14.78B
Pathfinder B 6 105,848,853 17,641,476 206.0 µs 0.0000% 96% 2.54B
Pathfinder C 8 106,447,096 13,305,887 268.2 µs 0.0000% 91% 2.55B
IV

Scaling

would more workers add throughput?
010M20M30M40M50M02.557.51012.51517.520Worker processes per clientThroughput per worker (paths/hr)Pathfinder B: 6 workers, 17.64M/hr per workerPathfinder BPathfinder C: 8 workers, 13.31M/hr per workerPathfinder CA New Beginning: 16 workers, 38.49M/hr per workerA New Beginning

Near-linear scaling — headroom to add workers

Per-worker throughput holds roughly steady as worker count rises, so each added worker contributes close to a full worker's output. Adding more workers (or clients) should increase total throughput proportionally.
Signals: per-worker vs workers r = 0.94, total vs workers r = 0.98, avg 23.15M/hr per worker.

V

The fleet, machine by machine

every client, reachable or not
Table 2. Each client's performance.log as read at build time. The sparkline traces throughput (paths/hr) across the log; unreachable clients are flagged, not dropped.
ThroughputClientStatusWorkers PathsInterestingRateNow /hrPeak /hr ComputeLast entry
— Pathfinder A unreachable — — — — — — — unreachable
Pathfinder B active 6 293.35B 5.3K 0.000% 105.85M 25.84M 695d 22h 5m ago
Pathfinder C active 8 292.49B 5.3K 0.000% 106.45M 26.66M 930d 12h 5m ago
— HP Laptop unreachable — — — — — — — unreachable
A New Beginning stale 16 77.51B 1.4K 0.000% 615.88M 39.17M 85d 5h 16d ago
Fleet total3/5 30 663.35B 12K 0.0000% 828.18M 39.17M 1711d 15h 2026-11-01 13:52
Compiled from the fleet telemetry · schema v1 · reads each client's performance.log. Set in Palatino. All measurement, no decoration.