1000 nodes and beyond: updates to Kubernetes performance and scalability

Re:1000 nodes and beyond: updates to Kubernetes performance ... by rodionos on Monday March 28, 2016 @03:56PM (#11376882)

The frame at 2:37 shows avg response time of 1.75 ms at 10 mln QPS. Which API call was measured? I'm looking at bar charts under "Metrics from Kubernetes 1.2" and the latencies graphed there appear to be different/higher.

[ Parent | on HN ]

Re:1000 nodes and beyond: updates to Kubernetes performance ... by a-robinson on Monday March 28, 2016 @05:14PM (#11377451)

"Metrics from Kubernetes 1.2" is discussing the latency of requests to the Kubernetes API (for managing what's in the cluster).

The latency referred to in the demo is the latency of requests from the loadbots to the nginx containers running in the cluster.

[ Parent | on HN ]

Re:1000 nodes and beyond: updates to Kubernetes performance ... by boulos on Monday March 28, 2016 @04:14PM (#11377007)

That's the nginx response time. You can see that when he scales up the loadbots but not the backends and says that the "tail latency has gotten quite high" (about 1min in).

[ Parent | on HN ]

Re:1000 nodes and beyond: updates to Kubernetes performance ... by roberthbailey on Tuesday March 29, 2016 @01:15AM (#11379610)

Correct. In addition, the source code used to run the demo is available on github at https://github.com/kubernetes/contrib/tree/master/scale-demo

[ Parent | on HN ]

Re:1000 nodes and beyond: updates to Kubernetes performance ... by rodionos on Tuesday March 29, 2016 @12:26PM (#11382636)

Thanks, all clear now.

[ Parent | on HN ]