Hacker News Reader

It would make sense to apply these optimizations to any kind of startup since presumably anticipating resource allocation ends up as a cost savings and improvement in user experience regardless of the base OS. There are plenty of Linux AMI images that are bloated and slow to start.

View on HN

It would only be practical to do this for very commonly used AMIs that AWS create and provision themselves. Commonly used because you don't want unused AMIs languishing in the instance pool long term. Only their own, because these AMIs are heavily manipulated and then customised for the user so you have to be positive the AMI is compatible with the manipulations.

I wonder if Azure does something similar.

According to a comment on my blog post - it seems that Azure do something similar as well. It would be pretty easy to verify

From my limited use of Azure I'd guess yes, because it also was hot-n'ready in under 5 minutes any time I needed a new instance.

Reply on news.ycombinator.com