2 ms·
I'm really struggling with connecting his conclusion to what we know of his workload. Can someone spell it out for me? He has many idle pods with a bursty wor
by jayd16 7y ago
I'm really struggling with connecting his conclusion to what we know of his workload. Can someone spell it out for me?
He has many idle pods with a bursty workload.
The author says they need to reserve a lot of cpu or containers fail to create. Why is this? Wouldn't memory be more likely a cause for the failure? How does lack of CPU cause a failure?
Later the author notes that a many core machine is good for his workload because "pods can be more tightly packed." How does that follow? A pod using above the reserved resources will bump up against the other pods on that physical machine whether you've virtualized it as a standard-1 or standard-16. Is there a cost savings because the unreserved ram over-provisioned? Wouldn't that overbooking be dangerous if you had uniform load across all the pods in a standard-16.
Said another way, why is resource contention with yourself in a standard-16 better or cheaper than with others in the standard-1 pool?
My understanding with going the vCPU options was simply the choice between pricing granularity and CPU overheard of k8s.
- dilyevsky 7y agoIt’s a bit hard to unpack as there seem to be multiple unrelated things there but i think the gist is classic problem of smaller nodes causing more resource fragmentation. The solution to increase node size is also classic and easy enough in cloud environment but has its tradeoffs as well (like lower reliability)