From 67e3d2b86edf85689b16713055dc1678239ff52d Mon Sep 17 00:00:00 2001 From: Dalton Hubble Date: Sat, 4 Nov 2017 14:08:20 -0700 Subject: [PATCH] docs: GCE network bandwidth is excellent, even btw zones * Remove performance note that the GCE vs AWS network performance is not an equal comparison. On both platforms, workers now span the (availability) zones of a region. * Testing host-to-host and pod-to-pod network bandwidth between nodes (now located in different zones) showed no reduction in bandwidth --- docs/topics/performance.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/topics/performance.md b/docs/topics/performance.md index 1884f0c4..b4153695 100644 --- a/docs/topics/performance.md +++ b/docs/topics/performance.md @@ -38,7 +38,6 @@ Network performance varies based on the platform and CNI plugin. `iperf` was use Notes: * AWS is alpha -* AWS instances are located in the same region. Google instances are located in the same zone (helps bandwidth at the expense of fault tolerance). * Network bandwidth fluctuates on AWS and Digital Ocean. * Only [certain AWS EC2 instance types](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/network_mtu.html#jumbo_frame_instances) allow jumbo frames. This is why the default MTU on AWS must be 1480. * Between Flannel and Calico, performance differences are usually minimal. Platform and configuration differenes dominate.