Comments on: Kubernetes Clusters Have Massive Overprovisioning Of Compute And Memory

By: Emanuel

Sun, 21 Jul 2024 13:21:30 +0000

Sounds like a management problem and human issue.

And don’t build your architecture on inefficient and wasteful languages. Examples of inefficient languages are Java, C#, NodeJS, anything that run on top of a runtime environment.

Languages that compiles into machine code and run directly on the iron is where you find efficiency and maximum resource utilization.

]]>

By: Jeremy H

Mon, 11 Mar 2024 00:25:42 +0000

IBM’s Turbonomic has been doing this for 5 years on k8s, and longer on x86.

]]>

By: Andy Chow

Thu, 07 Mar 2024 23:49:35 +0000

Average doesn’t mean much. Is the peak use near 100%? I don’t care much about average use, I’m more concerned about sudden volume change. A lot of things happen at some peak hours or some time of month. Very few workloads will be near constant. Even Netflix, I’m sure more people use it at 7 p.m. than at 4 a.m.

]]>

By: Calamity Jim

Tue, 05 Mar 2024 13:58:21 +0000

As Eric wrote, it could be difficult to max out all CPUs given the potential bottleneck issues. Also, though, I think the pricing model for cloud might benefit by considering the number of CPUs as one component, and the amount of energy used as another (if it doesn’t already do that). One would be paying less for X CPUs at 13% utilization, than for X CPUs at 64% utilization for example. We certainly do have this sort of overprovisioning of power in motorized vehicles, just in case (Hellcat Demon SRT for the occasional quick getaway), with running costs based mostly on energy consumed.

]]>

By: Eric Olson

Mon, 04 Mar 2024 16:34:31 +0000

While increasing CPU use sounds good, my understanding is typical server hardware often doesn’t have enough I/O and memory bandwidth to support all CPUs running at near capacity anyway. Maybe the reason one container benefits by using more CPU is only because the other containers haven’t already chewed up all the bandwidth.

In other words, what’s important is maximizing the throughput and that may be different than increasing CPU use. Of course this only makes tuning a kubernetes cluster more complicated and important.

]]>