4 ms·
took at look at these benchmarks. they appear to be using some extremely antiquated code, and workloads, that do not take advantage of any of the advanced featu
by spoaceman7777 2y ago
took at look at these benchmarks. they appear to be using some extremely antiquated code, and workloads, that do not take advantage of any of the advanced features and instruction introduced over the past 15-20 years in the x86-64 architecture.
additionally, the only updates they appear to have made in the last 5+ years involve optimizing the suite for Apple chips.
thus, it leaves out massive parts of modern computing, and the (many) additions to x86-64 that have been introduced since the 00s.
i'd encourage you to look into the advancements that have occurred in SIMD instructions since the olden days, and the way in which various programs, and compilers, are changed to take advantage of them
ARM is nice and all, but the benchmark you've linked appears to be some extremely outdated schlock that is peddled for $1000 a pop from a web page out of the history books. Really. Take a look through what the benchmarks on that page are actually using for tooling.
I'd consider the results valid if they were calculated using an up to date, and maintained, toolset, like that provided by openbenchmarking.org (the owner of which has been producing some excellent ARM64 vs Intel benchmarks on various workloads, particularly recently).
- PUSH_AX 2y agoDoes optimising the tests towards one architecture seem like a fair way of testing?
- kaba0 2y agoIt's optimizing as in previously it had far less attention.
- GeekyBear 2y ago> the only updates they appear to have made in the last 5+ years involve optimizing the suite for Apple chip How do you theorize that generic C or C++ code that you compile using GCC has been "optimized for an Apple chip"? Feankly, it's impossible to take any of this comment seriously.