News for hackers. Stuff that matters.
Re:Hypernetes: Bringing Security and Multi-Tenancy to Kubern... by switchbak on Wednesday May 25, 2016 @03:07AM (#11768137)
They mention that this helps cure some issues with regards to resource sharing / memory usage, etc. But does each VM still have a static allocation of memory?

One of the main benefits I have now is that if I run a number of containers that all take various amounts of memory, I can just throw them on and they share memory amongst each other quite efficiently. If I have to make a static allocation of memory for a VM, I'll typically choose a conservative memory number, and usually under-utilize the machine, wasting a lot of memory per-instance. Not so bad since I chose per-pod, but still an issue.

As it happens, this same issue is why I'm leaning towards lightweight native applications these days instead of an aggressive greedy virtual machine that grabs a bunch of heap. Golang/Rust in particular.

Re:Hypernetes: Bringing Security and Multi-Tenancy to Kubern... by scprodigy on Wednesday May 25, 2016 @06:23AM (#11768768)
Actually, scaleup is pretty easy for both VM and Linux container. But scale-down is very troublesome for both.

And the scheduler will need the mem size (not right now, but inevitable)