Benchmark Bandwidth Units #1051
Labels
No labels
announcement
bug
build
CI
dependencies
documentation
duplicate
enhancement
experience feedback
feature request
github_actions
help wanted
install
invalid
Long-term
optimization
portability
question
target-specific
test issue
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-Cyan4973/xxHash#1051
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
It can be observed from lines such as:
github.com/Cyan4973/xxHash@38d555879f/tests/bench/benchfn.c (L32)and:
github.com/Cyan4973/xxHash@38d555879f/tests/bench/main.c (L69)that MB and MiB in benchmarks both mean 2^20 bytes instead of 10^6 bytes.
This in turn suggests that it's likely that documentation reported bandwidths in GB/s are instead really in GiB/s, and should be ~7% higher for metric GB/s (the bigger number is often why internet and storage companies use metric units).
Well, not the same.
M means 'mega' ie. 10^6.
Mi means 'mebi' ie. 2^20.
megabytes vs mebibytes
Thats the point. One also has to be aware that some products have long term systemically used an incorrect definition. Such things should at the very least be maintained to be consistent. Notorious examples are:
It used to be that MB and GB clearly meant 2^20 and 2^30 respectively.
Up to the 2000's, there was no doubt about the meaning of these terms.
Then things changed. Some actors (Apple notably, the storage industry), decided that using 10^6 and 10^9 instead would make their numbers bigger, and therefore better than competition. I have vivid memories of "tech" articles (effectively fanboys trolls) from circa 2010 that explained that Apple drives had more capacity than Windows ones, based on this deliberately confusing metric difference.
And then, well, everybody else had to follow suit to not be on the loosing end.
And now we have to use MiB and GiB to mean what MB and GB originally meant.
I look forward to the moment I'll be able to buy my next pack of 34.36 GB of RAM.