I agree on Dhrystone, although it can still produce useful data about the microarchitecture, but not C-ray. C-ray may be small, but it actually does something useful using calculations that are done all the time in "real world apps". It's one of the most widely run benchmarks there is. It's basically taking a small part of what apps like pov-ray do and isolating those calculations for an easy to compile (thus making it widely compatible) benchmark.
Did I say it is useless? I said it is a microbenchmark.
Isn't this a big part of the issue for ARM though. If you say we have to limit benchmarks to only applications that have equal optimizations for x86 and ARM, despite decades of x86 dominance in the server and desktop market, your available test suite is going to be severely limited and also unrealistic if you are wanting to switch to actually using ARM.
Yes that's an issue. But we are comparing micro-architectures. You want to have an as fair comparison as possible, so you try to pick software that has the same level of optimization on both architectures, and compilers that are as close as possible. As I said it's like picking benchmarks where Intel cheated for a comparison against AMD; do that if you want but don't expect to be trusted except by fanatics who don't turn their brain on.
So no tests that Epyc inherently does well in either, got it. OpenSSL is (as the name suggests), open source so ARM vendors are free to analyze and contribute code if they think the code isn't optimized well for ARM.
I'm tired of this, really. I have not excluded these benchmarks, go re-read what I wrote instead of putting words in my mouth. I'm just characterizing the benchmarks, but if you have difficulty understanding this, it's either me being unable to convey my point of view, or you being obtuse (or biased).
It was 67% faster and using an older version of GCC versus the just released AOCC which was built upon the just released LLVM so I expected a very healthy uptick in performance same as if they had tested against the older version of LLVM. With that said, that's probably still too high for "real world" results which I pointed out in my reply to Mark. However, using an older version of GCC where AMD doesn't upstream optimizations is also not a fair comparison either for Rome which was my whole point from the beginning.
Agreed, but that's not a reason to setup an unrealistic AOCC vs gcc comparison on SPEC as you did. We all know that icc is cheating and should not be trusted, so why should we even talk about AOCC on SPEC? Because we all love AMD? Because we don't believe ARM is good at anything? Because ARM fans are a pain in a place forum rules don't allow me to mention?
I think that my point boils down to this: your initial comparison, no matter how many warnings you put around it, was meaningless and was taken as a proof of an unrealistic advantage of Rome by dumb AMD fanatics.
AMD would probably greatly benefit by working a lot more with the upstream effort of LLVM and especially GCC. I'm guessing that as AMD continues to improve financially, you'll see more of these types of efforts, just like they are finally getting around to working on fixing their vector paths with glibC.
www.phoronix.com
Yeah AMD finally moving years after others did, it's a very good thing. Too bad they couldn't realize earlier that spending $200k a year for a good SW engineer was all that was needed to get low hanging fruits (and ARM are guilty of the same mistake). But if you think that their AVX/AVX2 changes or other libc tweaks will give a significant speedup on SPEC int, well I won't convince you of anything.
You are also creating a pretty large strawman with your 2x speed-up comment which I not only never said, but I had already mentioned previously that comparing the published SPEC results in comparison to the Graviton2 Anandtech results showed an unrealistic advantage to Rome,
The almost 2x speed up (well OK 1.7x, 300 for AOCC vs 180 for gcc) is not a comment you made it's data from ServeTheHome. You know like an evidence that AOCC is so much faster that they are surely playing tricks that make any comparison with such results so pointless no one should make one even with a warning.
but I appreciate the digs at my character.
My English is not good enough to get this
But if you think I'm trying to insult you or whatever, I'm not and I'd be sorry if you thought so. I'm just frustrated that we obviously are in agreement on most things except that I think your original comparison was pointless (and I miserably failed at convincing you).
I suppose the proof will be in the pudding as they say and we'll have to see how many contracts the Ampere and TX3 chips end up winning.
Except that few will get that data (and are under NDA as I am).