zlacker

I know a good way to make a process make the most of the hardware and play cooperatively with other processes: don't use virtualization.

I will never understand the whole virtual machine and cloud craze. Your operating system is better than any hypervisor at sharing resources efficiently.

>>mgauna+(OP)
> cloud craze.

Automatic scaling is great. Cloud parallelization (a.k.a fork) is absolutely wild once you get it rolling. Code deployments are incredibly simple. Never having to worry about physical machines or variable traffic loads is worth the small overhead they charge me for the wrapper. The generic system wide permissions model is an absolute joy once you get over the learning curve.

>>mgauna+(OP)
I want to segregate, not to share.

>>mgauna+(OP)
In this context (the blog post) and the reason firecracker was created, was to isolate workloads.

And if youre running untrusted code, then using a virtualized environment is the easiest (id even say best) way to go about it.

>>mgauna+(OP)
After reading the README of virtualization tools (and looking at the author) I discovered the benefits of using them. I recommend also giving that a try.

>>Freedo+hE
I do have to use it since someone early on in the company I work at decided to do everything with AWS and Kubernetes.

The fact of the matter is that it's just inefficient, slow and expensive.

Bare metal is simple, fast, and keeps you in control.

>>mgauna+s71
bare metal has high capex and low opex

cloud vms have low capex and high opex

which one is more expensive is a function of many variables

>>presei+qE2
to get decent prices for cloud you need to commit to 3 years of usage upfront, and if you do that then it's about the same price as buying the hardware outright.

Otherwise it's three times more expensive.