4 ms·
CPU Cache contention, network overhead introduced by Kubernetes service proxy model, even the liveness checks. We haven’t yet evolved Kubernetes services to pr
by smarterclayton 8y ago
CPU Cache contention, network overhead introduced by Kubernetes service proxy model, even the liveness checks.
We haven’t yet evolved Kubernetes services to prefer specific cores and avoid app workloads quite yet (although cpu management is getting closer).
Docker is also somewhat hefty memory wise and you may contend on disk if not careful.
5% seems pretty reasonable to me in general, just as a consequence of having something heavier weight on the same node managing workloads.
- a-robinson 8y agoYeah, it appeared to just be general resource contention from having to share the machine -- CPU interrupts, less memory available, etc. I'll note, though, that the 5% number is when using host networking for both Cockroach and the client load generator. Using GKE's default cluster networking through the Docker bridge is closer to 15% worse than running directly on equivalent non-Kubernetes VMs.