Skip to content
NewSee how fast an edit goes live on this site
Halftone

EngineeringPerformance

A field guide to the sandbox runtime

The constraint, the fix, and the numbers before and after.

A field guideto thesandboxruntimeHALFTONE / JOURNAL
Cam Okafor
Published 2 min read

We kept the old path running next to the new one for two weeks and compared outputs byte for byte. Most differences were harmless. Three were real bugs that the old path had been hiding for years. This post covers what we changed, why, and what it means for you.

#What's next

For most of last year, a full build took eleven minutes. Nobody decided that was acceptable; it simply grew there, one dependency and one test suite at a time, until waiting became part of the job.

Caching is easy to add and hard to trust. The rule we settled on is simple: a cache key must include everything that can change the output, and nothing that cannot.

None of this needed a new framework. It needed a clear owner, a dashboard people actually looked at, and permission to delete code that no longer earned its keep.

“Good defaults are invisible until they are missing.”
Cam Okafor

#The details

We started by measuring instead of guessing. Every step got a timer, every run wrote its numbers to a table, and within a week the picture was clear: most of the time went to setup, not to the work itself.

Latency at the median improved, but the tail is what people feel. Our p95 dropped from 4.1 seconds to 900 milliseconds, and support tickets about slowness fell by more than half.

  • Keep the previous version one click away
  • Report problems in plain language
  • Skip what has not changed

#What changed

The part we underestimated was rollback. A faster pipeline is only better if you can undo it just as fast, so every deploy now keeps the previous version warm and one click away.

The fix was less clever than we expected. We cached what never changes, skipped what had not changed, and stopped doing work in series that could happen side by side.

StepBeforeAfter
Install94s12s
Build41s7s
Deploy18s4s

#What we would do differently

We kept the old path running next to the new one for two weeks and compared outputs byte for byte. Most differences were harmless. Three were real bugs that the old path had been hiding for years.

For most of last year, a full build took eleven minutes. Nobody decided that was acceptable; it simply grew there, one dependency and one test suite at a time, until waiting became part of the job.

  • Report problems in plain language
  • Run independent steps in parallel
  • Skip what has not changed
  • Keep the previous version one click away