3 ms·
> I'll note though that different users have different targets. Some people care about "time from request to first instruction ticks over" while others only car
by dmitriid 4y ago
> I'll note though that different users have different targets. Some people care about "time from request to first instruction ticks over" while others only care about "time from request to ssh'able from the public internet".
This is the same target: a machine (that usually only has single app on it) shouldn't take more time to boot than a general-purpose consumer PC/laptop.
The reason it takes so darn long to start in so many cases is just how horrendously overcomplicated the whole cloud setup is internally and externally (sometimes for good reasons, sometimes because we don't know better, sometimes just because it really is just overly complicated and overengineered)
- nousermane 4y ago> shouldn't take more time to boot than a general-purpose consumer PC/laptop. That's an incredibly easy target. VMs can and should boot much faster than that - just look at firecracker hypervisor. Even with KVM, if you replace systemd with something small and simple [0] (which you totally should, for single-app VMs), boot times of couple of seconds are within reach. [0] https://github.com/Yelp/dumb-init https://github.com/Yelp/dumb-init
- dmitriid 4y agoI'm still sad nanokernels or nanokernel-like never took off. I also remember clicking around Ling (Erlang on Xen, sadly no longer active [1]) where the whole VM could boot up, service the request, and shut down in less time than it takes a cloud to start spinning up an instance :) [1] https://github.com/cloudozer/ling https://github.com/cloudozer/ling