4 ms·
A container that is idle and do not serve any request only really as memory in its footprint. There is no reason having tens or hundreds of processes not occupy
by prmoustache 3y ago
A container that is idle and do not serve any request only really as memory in its footprint. There is no reason having tens or hundreds of processes not occupying cpu and i/o time would affect battery life in a significant manner.
- klohto 3y agoBro and where do you think the containers and scheduler run? There is a whole linux underneath running all the time
- prmoustache 3y agoOnly one kernel and scheduler for all the containers, that doesn't have a lot to do if most of the processes are idle. And I am not your bro.
- klohto 3y agoYour whole argument is containers will not occupy CPU or I/O. Which is not true, you’re running a full fledged VM, not just a kernel. And presumably the person running k8s is probably not running them to have them idle. They are technically knowledgeable enough to be aware how much resources do they consume, and be excited for such comparison.
- prmoustache 3y agoA linux VM with only a kubernetes/docker with most workloads idling doesn't use a lot of resources, except memory, probably less than the typical open browser tab full of unoptimized js. When you have kubernetes on your laptop, that is to test your code alongside a set of other microservices functionnally representative of a prod deployment. That doesn't mean your containers will have much load appart from your own punctual testing.