You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should decide the standardisation of units through the simulation. We should further decide on the i, so either KiB or KB (no matter what if K or M or G or ...). Currently I think we use GB.
Concerning the storage size, I recommend deciding on one data size unit and sticking to it. If we use Bytes then float is enough to represent up to 8 PiB precisely increasing with the prefix (e.g. 8 EiB for KiB base); Since there are no fractional Bytes, using int would allow for arbitrarily large and precise storage size even when using Bytes.
Using plain bytes has the least problems in standardisation (we do not need to decide on KiB versus KB etc.) and is always precise when using int. However, it might degrade to float during naive computations, which is imprecise beyond 8PB.
We should decide the standardisation of units through the simulation. We should further decide on the i, so either KiB or KB (no matter what if K or M or G or ...). Currently I think we use GB.
Originally posted by @maxfischer2781 in #53
The text was updated successfully, but these errors were encountered: