CadolesKube
/
typhoon
mirror of https://github.com/puppetmaster/typhoon.git
7
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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
This commit is contained in:
Dalton Hubble 2017-11-04 14:08:20 -07:00
parent a48dd9ebd8
commit 67e3d2b86e
1 changed files with 0 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
docs/topics/performance.md
View File

@ -38,7 +38,6 @@ Network performance varies based on the platform and CNI plugin. `iperf` was use
Notes: Notes:
* AWS is alpha * 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. * 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. * 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. * Between Flannel and Calico, performance differences are usually minimal. Platform and configuration differenes dominate.