How I Learned to Stop Worrying and Love the Sandbox — Matt Brockman, E2B
This workshop provides a deep dive into the operational challenges of running large-scale, isolated code execution environments using sandboxes (specifically E2B). The session walks through deliberate failures—such as runaway processes, memory leaks, and disk filling—to demonstrate best practices for resource management, state persistence, and process cleanup. Key architectural topics include snapshotting the system state, managing sandbox lifecycles (idle timeouts), and implementing user-specific workspace mapping to handle thousands of concurrent workloads.
Key takeaways
-
Sandbox Fundamentals
4:51
Sandboxes provide isolated, user-specific execution environments, preventing code from interfering with other users. E2B aims to spin up sandboxes in less than 100 milliseconds (2:51).
-
State Persistence via Snapshots
5:11
Sandboxes preserve a running system's state by snapshotting both memory and the filesystem, allowing work to pause and resume seamlessly, which is crucial for long-running agent tasks (2:51).
-
Resource Leak Mitigation
30:43
Common issues include processes consuming excessive CPU (e.g., 99.7% usage), memory pressure, and filling the disk. These require identifying and terminating rogue processes (18:43, 20:30, 21:57).
-
Sandbox Lifecycle Management
31:14
To manage costs and resources at scale, it is necessary to set a long runtime for a task but implement a short idle timeout, allowing the sandbox to shut down after the task completes (31:14).
-
Scaling Workspaces
44:00
For large deployments, the assignment mechanism should move beyond simple round-robin assignment to maintain a persistent mapping of users to specific sandbox IDs (44:00).