Wow!  I knew there was confusion out there about this, but I didnt realize
just how much (even on my part it would seem).  Hereís one possible source
of clarification:

and another:
(not this Scott's newsletter by the way - I just happened across it doing a
yahoo search on the matter)

The consensus seems to be that there should be made a distinction between a
"binary Kilo" (with a capital ďKĒ) and a "decimal kilo" (with a lower-case
ďkĒ).  This, I think, was already well-established and agreed to but it sure
is easy to get sloppy with that capitalization and terminology.

kbit = 1,000 bits (decimal 10^3)
kByte = 1,000 bytes (decimal 10^3)

Kbit = 1,024 bits (binary 2^10)
KByte = 1,024 bytes (binary 2^10)

As I understand it, most modern hard drives are now rated in decimal format
(Iím pretty sure it used to be binary, but Iíve read in several different
places that the industry migrated to decimal sometime back -- probably as a
marketing gimmick).  That is, 1 kByte (or even KByte in this special case)
of storage actually equals 1,000 Bytes or 8,000 bits instead of 1,024 Bytes
or 8,192 bits.  Memory is apparently still rated in binary Kilo bits/Bytes. 
That is, 1 KB of memory is 1,024 Bytes or 8,192 bits.

All WAN connections always have been and still are rated in decimal format. 
That is, 1 kbps equals 1,000 bits/sec and 1 kB equals 1,000 Bytes (or 8,000
bits)/sec.  I'm not aware of throughput ever having been expressed in binary
Kbits or KBytes (at least not in the "telecom" world).  Maybe computer geeks
did that, but it only served to confuse the matter more if they did.  If a
download test were to return results in true binary KBytes/sec, you would
first have to multiply that number of KBytes by 1,024 and then multiply by 8
to get the true decimal number of bits/sec.  Perhaps tests some do.  Perhaps
some donít.  Probably itís a mess of a mix that resulted from all this

Software weenies still seem to deal with binary Kilo, regardless of whether
itís bits or Bytes.  But Iím not one of them, so I canít make this last
statement definitively.



Message Posted at:
FAQ, list archives, and subscription info:
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to