Inside Orchard
The build queueHow it works
Long, heavy jobs, such as tests and builds, go from the Mac you work on to a spare Mac on the same network.
Touch the spare's keyboard or mouse and the job pauses. It carries on about three and a half minutes after you stop.
A job no machine can run correctly is refused with a reason. If the spare disappears for about 15 minutes, waiting jobs run on the main Mac.
Next: What we measuredWhat we measured
-
Proven
A small Swift package built on the spare Intel Mac in 148 s cold, about 10 s with the cache, and 2.4 s after an edit to one file.
-
Proven
Running jobs at background priority cost about 2.4 times the throughput, so jobs now run at full speed unless asked otherwise.
-
Proven
The fast Apple silicon Mac runs Orchard's benchmark about 3 times as fast as the old Intel one.
-
Proven
Orchard takes 105 MB on the spare Mac in all.
-
Proven
A large model split across our own machines answered at 4.2 words a second, below its estimate of 4.8.
What broke
-
Proven
A weak 8 W charger drained the spare Mac's battery under load while it still reported mains power. Orchard now pauses jobs below 20% battery even when plugged in.
-
Proven
Opening a new SSH connection for every check drove the spare Mac's directory service to about 23% CPU. Connections are now reused.
-
A guess
Whether to run jobs only at night is still open.
Why we built it
A fast Mac always in use, an old Intel Mac sitting idle, and AI coding agents running tests and builds all day.