Speeds and Data Plans
I'm researching data plans and noticed Cox updated and reformatted their Speeds and Data Plans page. A couple notes:
Gigablast Package & Maximum Limit. Cox defines an area with "periods of sustai...
Forum Discussion
when 1024 is the base multiplier
1024 what? Where'd you get 1024?
In decimal (base 10), 1 Kilobyte = 1000 bytes
In binary (base 2), 1 Kilobyte = 210 = 1024 bytes (1000 * 1.024)
1.25 TB (base 2) = 1250 GB (base 2)
1.25 TB (base 10) = 1250 billion bytes = 1250 GB (base 10)
1.25 TB (base 2) = 1250 billion * 1.024 = 1280 billion bytes = 1280 GB (base 10)
1.25 TB (base 2) = 1280 GB (base 10) because Cox is mixing two, different bases.
The individual who drafted verbiage for the Cox webpage might have only been told monthly data plans are to have a 1.25 TB data limit. If so, assuming it was a binary amount may or may not have been correct. Either way, the "1,280 GB" was probably included to provide a more relatable decimal GB amount, but base mixing made it confusing. The monthly data limit is most likely 1.25 TB binary (1280 GB decimal), but clarification from Cox would be needed to confirm that .
base mixing made it confusing
It can be confusing...but an erroneous $10 penalty would quickly clarify.
2^10 does equal 1024. 1024 what? 1024 bits. One thousand & twenty-four 1's and 0's. 1024 is an expression of the binary numbering system: 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, 1024, 2048, etc.
However, as soon as you started notating as "bytes," you departed the binary numbering system by dividing the binary expression with 8. Whenever we notate as kB, MB, GB, TB, PB, EB, ZB, YB, etc...it's base-10.
However, as a side note, if you want to remain within the binary numbering system to express big numbers, you must use binary prefixes: KiB, MiB, GiB, TiB, PiB, EiB, ZiB, YiB, etc.
This is where you went wrong: 1.25 TB (base 2) = 1250 billion * 1.024 = 1280 billion bytes = 1280 GB (base 10)
• Because of the "B," 1.25 TB is not a binary expression (base-2)
• 1.25 TB does = 1250 billion in the decimal numbering system
• However, you multiplied the base-10 expression (1250) by a kilobit'd base-2 expression (1.024) to get an erroneous hybrid value (1280).Why multiply...just use 1 system.
I understand this is highly trivial, maybe even nonsensical, to some readers. For example, if we're comparing kilobits to kilobytes, the numerical difference is a paltry 2.4%. Who cares, right? However, when we venture into the "tera" territory (sorry), the differences get significantly greater.
At which point would Cox start "automatically" charging $10: 1.25 TB or 1280 GB? If Cox penalized you at 1.25 TB, you'd have a legitimate gripe because you hadn't reached 1280 GB. Maybe the $10 is trivial.
This has devolved into another stupid conversation.
2^10 does equal 1024. 1024 what? 1024 bits.
There are 1024 bytes in a kilobyte (KB) using conventional metrics.
This is where you went wrong: 1.25 TB (base 2) = 1250 billion * 1.024 = 1280 billion bytes = 1280 GB (base 10)
• Because of the "B," 1.25 TB is not a binary expression (base-2)
• 1.25 TB does = 1250 billion in the decimal numbering system
• However, you multiplied the base-10 expression (1250) by a kilobit'd base-2 expression (1.024) to get an erroneous hybrid value (1280).1.25 TB (base 2) = 1250 billion * 1.024 = 1280 billion bytes = 1280 GB (base 10)
The above statement is accurate. You misinterpreted it. It was included as-is to to maintain a standard presentation with the other methods listed. Base 2 indicates the calculation is based on a binary KB with 1024 bytes. The references are to amounts of data transmitted, not transmission rates. TB is appropriate to represent an amount of data, regardless of the base used in the calculation.
A binary KB is 1024 bytes and a decimal kilobyte is 1000 bytes. My calculation determined the decimal equivalent of a single binary byte by dividing the size of a binary KB by the size of a decimal KB. 1024/1000 = 1.024. I then multiplied the 1.024 factor by the size of decimal 1.25 TB (1250 billion bytes) to get the 1280 GB size of 1.25 TB with a binary KB.
1000 * 1000 * 1000 * 1000 * 1.25 = 1250 Billion bytes (using decimal KB)
1024 * 1000 * 1000 * 1000 * 1.25 = 1280 Billion bytes (using binary KB)
1024/1000 = 1.024 * 1250 Billion = 1280 Billion bytes (using binary KB)
You get to the same place either way, but using the binary to decimal ratio highlights a binary KB is 1.024 times larger than a decimal KB.
MB calculation methods
Base 10: 1000 * 1000 = 1,000,000 bytes International Standard of Units (SI)
Mixed: 1024 * 1000 = 1,024,000 bytes Conventional metrics
Base 2: 1024 * 1024 = 1,048,576 bytes Computer storage
Cox used conventional metrics that report a larger amount than the more accurate decimal measure. But, we don't know if the webpage is accurate or if it's just how the webpage author interpreted the specs.
Conventional metrics
KB = 210 = 1024 bytes
MB = 1000 KB = 1,024,000 bytes not 1 * 1,000,0000 = 1,000,000 bytes
GB = 1000 MB= 1,024,000,000 bytes
TB = 1000 GB= 1,024,000,000,000 bytes
Data Units Converter
www.gigacalculator.com/.../data-storage-bandwidth-converter.php
With the "Use SI standard" box unchecked (conventional metrics), enter 1.25 in the box on the left and select TB, then select GB on the right. 1.25 TB = 1,280 GB
Now check the "Use SI standard" box (decimal) 1.25 TB = 1,250 GB
