Mixing memory unit messages

One of my pet hates is developers messing up units of memory.  In general, the difference doesn't matter much, or you can work out what they meant to say, but it does annoy me when developers who should know better appear to be confused about what they are trying to say.

From Wikipedia's Byte page, here is a cheat sheet of units

"b" means bits
"B" means bytes
"k" or kilo- is standard prefix meaning 1000
"K" or "Ki", sometimes called kibi- is 1024
"m" or mill-, means 1/1000th
"M" or mega-, means 1000^2
"Mi" or mebi-, means 1024^2

 Unit      Meaning      In bytes
mb    
milli-bits1/8000th of a byte
mB    
milli-bytes1/1000th of a byte
kb    
kilo-bits
125 bytes
kB    
kilo-bytes
1000 bytes
Kb or Kib    
kibi-bits
128 bytes
KB or KiB    
kibi-bytes
1024 bytes
Mb    
mega-bits
125,000 bytes
MB    
mega-bytes
1,000,000 bytes
Mib    
mebi-bits
131,072 bytes
MiB    
mebi-bytes
1,048,576 bytes

What annoys me is when professionals confuse these terms.

In UNIX:

In top on Unix it states
KiB Mem:  32893900

but when I do "head -1 /proc/meminfo" it states
MemTotal:       32893900 kB
this is 2.4% less.

I suspect top is correct as it is closer the amount of memory installed and they used "KiB" which lends credibility, but I can't be sure.

In the JVM

The default translation for "KBYTES" is "kbytes" but in Japanese and Chinese it is "KB" which is 2.4% more.

While the JVM appears to be using KiB or kibibytes every where, it refers to "KiB" only three times, but uses "kB" in twice, "Kb" in seven places, "KB" in 127 places and "kilobytes" in three cases.

Similarly "MiB" appears 4 times, "MB" in 87 places, "Mb" three times and "mb" three times.

Puzzle

Question: A computer program writes to memory at 49 mb/s, to disk at 50 mb/s and to the network at 100 mb/s. Which is it writing data at a higher rate to; the memory, the disk or the network?

Answer: It is probably writing to memory most and the network least.  This is because it might be read as "... to memory at 49 MiB/s, to disk at 50 MB/s and to the network at 100 Mb/s. " and one MiB/s is almost 8.4 Mb/s

Conclusion

If you don't know what units you have in mind and which ones you don't, it shouldn't be surprising if someone reading your output is confused as well.

I encourage everyone to use standard units in their code so when you see units you know exactly what they mean.


Comments

Post a Comment

Popular posts from this blog

Java is Very Fast, If You Don’t Create Many Objects

Image
  You still have to watch how many objects you create. This article looks at a benchmark passing events over TCP/IP at 4 billion events per minute using the net.openhft.chronicle.wire.channel package in Chronicle Wire and why we still avoid object allocations..  One of the key optimisations is creating almost no garbage. Allocation is a very cheap operation and collection of very short-lived objects is also very cheap. Does this really make a difference? What difference does one small object per event (44 bytes) make to the performance in a throughput test where GC pauses are amortised? While allocation is as efficient as possible, it doesn’t avoid the memory pressure on the L1/L2 caches of your CPUs and when many cores are busy, they are contending for memory in the shared L3 cache.  Results Benchmark on a Ryzen 5950X with Ubuntu 22.10. JVM Vendor, Version No objects Throughput, Average Latency* One object per event Throughput, Average Latency* Azul Zulu 1.8.0_322 60.6 ...
Read more

System wide unique nanosecond timestamps

A Unique Identifier can be very useful for tracing. Those ids are even more useful when they contain a high-resolution timestamp.  Not only do they record the time of an event, but if unique can help trace events as they pass through the system. Such unique timestamps however can be expensive depending on how they are implemented.   This post explores a lightweight means of producing a unique, monotonically increasing system-wide nano-second resolution timestamp available in our open-source library. Uses for Unique Identifiers Unique identifiers can be useful to associate with a piece of information so that information can be referred to later unambiguously. This could be an event, a request, an order id, or a customer id. They can naturally be used as a primary key in a database or key/value store to retrieve that information later. One of the challenges of generating these identifiers is avoiding creating duplicates while not having an increasing cost.  You could ...
Read more

What does Chronicle Software do?

Image
Overview Chronicle Software is about simplifying fast data.  It is a suite of libraries to make it easier to write, monitor and tune data processing systems where performance and scalability are concerned. But its free, how do you make money, through support? We offer premium support . However, we often hear from users for the first time about a year after they have it in production.  Most users find they can support the software themselves.  It is only after a year or so, they have questions or concerns about where to take the product next.  In many cases, it is to a problem we have already solved and they just need to upgrade their software or use a new module we have added. As we don't know who is using most of our software, we can't advise them on how best to use our software and what updates or enhancements they would benefit from. We need users to contact us and ask questions.  We have a free forum , and we respond to 50% of questions in 2 hours...
Read more