What is Binpacked?
A scheduling and memory overcommit layer for bare-metal and nested KVM fleets. It tracks what fits on each worker, reserves capacity for each launch, and puts a host agent on every worker to make memory overcommit practical. The point is more VMs per worker with your targets still met.
Do we have to replace our scheduler?
No. You can replace your VM scheduler with ours, or keep yours and use our capacity API. Either way Binpacked tracks what fits on each worker and reserves capacity for each launch, so concurrent requests cannot claim the same resources.
Does it need bare metal?
No. It runs on bare-metal KVM fleets and on nested KVM, where each worker is itself a virtual machine.
What is memory overcommit?
Promising guests more memory in total than a worker physically has, on the grounds that they never touch all of it at the same moment. The engineering is in deciding which guests take part, how far to go, and what happens when memory gets tight.
Isn’t memory overcommit risky?
It is when it is done blind. The host agent is there so that it is not. It protects guaranteed memory for sensitive workloads, lets only eligible VMs borrow spare RAM, and verifies that reclaimed memory has returned to the host before more work is admitted. It holds capacity back for boot bursts, and it tightens admission when a host fails or telemetry goes stale.
Why memory, and not CPU?
Because that is where the room is. When CPU is oversubscribed, things run slower. When memory runs out, something gets killed. So memory tends to be the resource a fleet is most careful with, and the one with the most idle capacity sitting in it. It is also the harder problem, which is why Binpacked puts a host agent on every worker.
How do we find out whether it is a good fit?
Ask us. We will collect the data from your fleet as it runs today: what is on each worker, how much memory guests are allocated, and how much of it they touch. Nothing changes while we do. Then we tell you whether Binpacked is a good fit, and we say so if it is not. Get in touch to start.
How many more VMs per worker?
It depends on two things: how much of a worker’s RAM is allocated to guests, and how much of that the guests actually touch. The calculator does the arithmetic with your inputs. We would rather collect the real numbers from your fleet than quote you an average.
What about warm sandboxes?
Planned, not shipped. The idea is that for warm sandboxes the host agent could recommend when to keep a guest resident, when to reclaim its memory, and when to ask the runtime to pause it. If that is your workload, we would like to hear how you run it.
Is any of this new?
No. Hypervisors have overcommitted guest memory for more than twenty years, and the largest fleets pack and overcommit as a matter of course. VMware described its approach in a 2002 paper, and Google described Borg’s in 2015. What is hard is doing it on your own fleet without missing your targets. That is the part Binpacked is for.