Compiler Explorer runs 92M compilations a year — here's how it works
blaizedsouza · x · 2026-09-19
Matt Godbolt details how Compiler Explorer operates at scale in 2025: 92 million compilations a year (1.8M weekly) across 3,000+ compiler versions and 81 languages.
Key points from the architecture walkthrough:
- Code typed into the Monaco editor (same as VS Code) travels via CloudFront and a load balancer, which routes to a healthy instance in the right cluster.
- Each instance queues up to 2 concurrent compilations, runs them inside an nsjail sandbox, then filters output, attributes source lines, and returns JSON to the browser.
- Cluster sizes auto-scale based on language demand (e.g. a flurry of Windows compiler requests scales the fleet within minutes).
More from coding & agent
- Power user burns 1bn tokens a day at 98.65% cache hits, weighing GLM-5.3 vs DeepSeek after Claude Code weekly limits — julianharris · 2026-09-19
- Two MCP orchestration patterns: Jev as LLM tool orchestrator vs LLM as a tool — blaizedsouza · 2026-09-19
- Jev controls Ableton Live by voice, ~40x faster than LLM computer use — jordiponsdotme · 2026-09-19
- Dev wires up a vLLM reproduction in minutes with Codex, runs it on DGX Spark — remilouf · 2026-09-19
- Dev builds Vercel-like tool to turn any project into a hosted MCP server with one prompt — Corridl · 2026-09-19
- Querit launches coding-focused search built for code agents and IDEs — SucceededMind · 2026-09-19