From the source
Agents don't deploy sandboxes ahead of time.
They create sandboxes on demand, for each task, expect them to be ready immediately, and be able to pause and resume.
So we rearchitected Containers to meet these requirements: your code can now choose each sandbox's image and instance type at runtime, Containers start 6x faster, and filesystem snapshots are available in public beta.
To make this possible, we’ve rethought the Containers infrastructure from the bottom up.
A new scheduling policy moves control over each sandbox into application code, while a redesigned runtime provides a faster path to a running Container.
In ComputeSDK’s independent benchmark, median startup fell from just over four seconds to 648 milliseconds, and, in our own preliminary tests, burst testing successfully created hundreds of thousands of containers in seconds.
All of this builds on what has always set Containers on Cloudflare apart: every Container gets its own Durable Object, a persistent, programmable controller running right next to it that manages its lifecycle, outbound traffic, and more.
…
