6 ms·
MB/s is probably incorrect for the EBS throughput instance limits; those values make more sense if they use Mb/s.
by nierman 11y ago
MB/s is probably incorrect for the EBS throughput instance limits; those values make more sense if they use Mb/s.
- deleted 11y ago[deleted]
- xeno42 11y agoThe page linked in the post confirms your assertion: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSOptimized.html https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSOptim...
- jeffbarr 11y agoBlog post author here - you are correct, I was wrong, and the fix is rolling out now!
- listic 11y agoGlad to see you following the discussion, Jeff. Maybe you probably could address my and others' curiosity re: the exact nature of the custom Intel Xeon E5-2676 v3 CPU? I don't think Intel could justify making any serious customization even for a customer as large as Amazon, but I would be very interested to know exactly how custom it is.
- ghshephard 11y agoUniversal request to all when doing technical documentation - "MBytes/sec" and "Mbits/sec" are much clearer, and leave only the doubt as to whether you mean 2^20 or 10^6 (and, in 95% of use cases, 10^6 is the correct choice, both syntactically, as well as in what you are actually measuring - data rates are almost always in SI units)