3 ms·
It'd be nice if the CPU graphs contained the y axis. The proportion is a large drop but it's unclear is that's 1000m to 100m or 4000m to 250m (a much bigger cos
by nijave 3y ago
It'd be nice if the CPU graphs contained the y axis. The proportion is a large drop but it's unclear is that's 1000m to 100m or 4000m to 250m (a much bigger cost reduction)
It also sounds like their knative solution is slowly getting flattened into a load balanced or "smart" L7 proxy.
Also curious is they submitted these changes upstream. Seems like a pretty clear use case with numbers behind it which usually helps with interest.
Finally, I really love a solution that net deletes code and makes everything faster (and simpler).
- redleather 3y agoHi there, my name is on the post! The CPU graph was a 500 (second) drop in the sum of CPU usage of kube-proxy pods alone. I think this is okay to disclose (we took out most y axes during final edits, this one seems to be a collateral). You're right about the flattening - since this work, we've taken out the pieces of knative we really needed. Right again about embedding some of those pieces in our L7 proxy. We didn't upstream the changes because we feel our use case is atypical - all KServices (Knative Services) only ever had one pod. This constraint enabled most of the simplifications we were able to make. On the last point - so do we!