Gigabytes vs. Gibibytes

We recently refactored our math and the presentation of disk usage. Each cloud provider uses different measures - some Gigabytes (base 10), others Gibibytes (base 2) - and over the years we had coded to their preference. However this produced inconsistencies in behavior and display. On top of that, the humans in the loop would sometimes think they had to do conversions between Giga and Gibi when they shouldn’t (for example when setting Team limits.) So we bit the bullet and did a significant code refactor, choosing to adopt the Gigabyte (base 10) measure as it was the more common nomenclature for users. This cutover also required some data clean up for the reported values for existing systems, and an audit of all Team limits.

If you feel the reporting for your Team or a given system is off, please contact support. Keep in mind that the operating system modifies the available space on a disk so it will not match up to the raw provisioned disk size.