3 ms·
Did they increase the per-instance network bandwidth caps? Previously instances had 2Gb/s/core of network bandwidth capped at 16Gb/s, which makes 8-core nodes
by cottonseed 9y ago
Did they increase the per-instance network bandwidth caps? Previously instances had 2Gb/s/core of network bandwidth capped at 16Gb/s, which makes 8-core nodes the sweet spot for network bandwidth.
I never quite understood why this is necessary if they're cutting up larger machines. Why should the total network cap matter if I have two 8-core instances or one 16-core instance on the same physical machine?
edit:
https://cloud.google.com/docs/compare/data-centers/networking https://cloud.google.com/docs/compare/data-centers/networkin...
"The egress traffic from a given VM instance is subject to maximum network egress throughput caps. These caps are dependent on the number of cores that the VM instance has. Each core is subject to a 2 Gbps cap for peak performance. Each additional core increases the network cap, up to a theoretical maximum of 16 Gbps for each instance. The actual performance you experience will vary depending on your workload. All caps are meant as maximum possible performance, and not sustained performance."
- brianwawok 9y agoI doubt the average mysql server needs more than 16gb of bandwidth.
- sqldba 9y ago... let me show you the queries the developers are writing ^^
- brianwawok 9y agoSo you need to fix the developers not upgrade your network cards :)
- cottonseed 9y agoI don't even know how to reply to this. MySQL isn't the only cloud workload.
- tgtweak 9y agoPretty simple to understand why, they're "guaranteeing" that bandwidth. The hosts have a finite amount of network bandwidth available, they also have a finite amount of cores. Judging by the ratio it's likely something such as 2x 56gbe network ports on the host (=112Gbps), which has 56 vcpu (2x xeon 14c/28T)
- cottonseed 9y agoRight. So that's 2Gb/s for every core so why top out at 16Gb/s? I get the per core limit not the instance limit.