Compiler Explorer: Behind The Scenes
summary
A web service that started as a shell script now runs on AWS with Node.js and Docker, serving about 1.17M compiles/week, hosting 400+ compilers (≈250 GB of binaries) and ~80k executions by sandboxing with firejail and moving toward nsjail. It adds features like a local build via make, execution support for running binaries, a conformance view across compilers, and performance inspection with LLVM MCA. Compilers are rebuilt daily with custom CI; the site scales and mostly works, but ops and caching failures still bite.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:33Origins of Compiler Explorer
- 4:38First web version
- 5:59Evolution and new features
- 11:03Code execution feature
- 13:14Advanced execution options
- 15:03Language comparison
- 16:40Assembly exploration tools
- 18:55Instruction set analysis
- 21:43LLVM MCA tool demonstration
- 27:58Conformance and validation
- 30:30Hidden features and tips
- 34:15Technical architecture
- 37:58Site statistics
- 40:32Maintenance and building
- 44:16Security and monitoring
- 48:28Past failures and lessons
- 52:19Future goals and conclusion
- 55:57Q&A
related talks
56mWhat's New in Compiler Explorer?
34mPanel Discussion: Browsers & Wasm
28mCode Anywhere, Share Everywhere: Wasm-Powered Dev Environments
50mOur Adventure building a massively scalable mixed C++ and Rust remote compiler cloud
16mArchitecting A Component Compiler
42mSupercharge Your Performance with the Optimus Cirrus Platform
58m"Just switch the compiler", they said
29mThe Return of Write Once, Run Anywhere