▲ | varjag 2 days ago | |||||||||||||||||||||||||
Decibels are not anywhere near as ridiculous as Marketing Kilobytes introduced in the 1990s. Pot, meet kettle. | ||||||||||||||||||||||||||
▲ | nayuki 21 hours ago | parent [-] | |||||||||||||||||||||||||
This is one of those cases where marketing is correct. Oh tell me, if your CPU processes 1 byte in 1 cycle, and it runs at 800 MHz, how many bytes does it process in 1 second? The answer is 800 million bytes, or 800 (real) megabytes. It cannot be 800 mebibytes. (Equal to 763 mebibytes.) Similarly, let's say we have a 1-bit Boolean attribute for each person in the world, and the world population is 8 062 000 000 billion people. How many bits do we need in our database? It's 8.062 gigabits, not 8.062 gibibits. (Equal to 7.508 gibibits.) The telecom industry has always used power-of-1000 prefixes on bits and bits per second. You have a gigabit Ethernet LAN, and assume no protocol overhead. How long does it take to transmit a 4.7 GB (real gigabytes) DVD image? Multiply by 8 to convert from bytes to bits, so that's 37.6 Gb, so that will take 37.6 seconds to transmit. But how long does it take to transmit a "700 MB" (actually MiB) CD image? Well, it's 734 MB (real megabytes), so 5872 Mb, which is 5.872 seconds. The problem with the abusively overloaded definition that 1 kilobyte = 1024 bytes, 1 megabyte = 1048576 bytes, etc. is that it fails to align with the rest of the metric system, or even how we group decimal numbers into thousands and millions. The computer industry is wrong here. And now you have the problem that you can't fit a memory dump of "16 GB" of RAM onto a "16 GB" flash memory card, because the former is actually GiB but the latter is real GB. | ||||||||||||||||||||||||||
|