Possible false file size?!

[DonaltDuck]

I was over the following:
No file size specified in the database (or the web pages) corresponds to the actual download file size!
Somehow all files are ~ 7% larger

Example:
https://www.betaarchive.com/database/vi ... b6f0deb0a5
Size 5.22 GB
real download size = 4.86 GB

Database size is always ~ 7% greater than real size

Now everyone may say: Actually, that doesn't bother

But, the dayly download limit is calculated with the 7% larger data.
i.e. I actually only get 46.5 GB city 50GB

@Andy can you please check this (maybe it is also a design bug)

TIA

[mrpijey]

GB vs GiB.



It's an never ending controversy which one to use, either the SI standard (1000^x) or the IEC 80000-13 standard (1024^x). Here we've defined it as the system addresses it and not by SI standards for simplification, therefore the "larger" size. In terms of actual transferred data it makes no difference as your speed is also SI standard.

The percentage difference increases as data sets gets larger.

Explorer shows both sizes, most other situations do not. Do a size check in cmd for example and you'll see it's 5 223 285 261 (rounded down to 5.22GB which is what's displayed on the DB). Which is also what we get when using php functions to calculate size.

Things should be either be shown in bytes only, or with GiB, MiB designations but that will most likely confuse people as most don't know what that is...

[Andy]

The database consistently uses SI standard (1000^x) throughout (1000 bytes to 1 kilobyte, and so on). How your operating system shows you the file size will differ.

[DonaltDuck]

THX a lot
Sorry, my mistake (I need glasses)
mea culpa, mea culpa, mea maxima culpa

Topic can be closed

[mrpijey]

The database consistently uses SI standard (1000^x) throughout (1000 bytes to 1 kilobyte, and so on). How your operating system shows you the file size will differ.

Yes, but sizes are not calculated by the OS using SI standard which gives you the larger size. Sizes are calculated with 1024^x because the OS reports it as such, we may do internal conversions in the DB with 1000^x but those will still at the end be based on a 1024^x size. Otherwise I would need to convert that data before it's written to the database. See the CMD comment I made above and you'll see why.