3 ms·
I mean the working set of the executable program is much larger than the processor's L1 instruction cache. Virtually all realistic cloud workloads (search, dat
by shereadsthenews 7y ago
I mean the working set of the executable program is much larger than the processor's L1 instruction cache. Virtually all realistic cloud workloads (search, databases, email, etc etc) meet this definition of "large" whereas almost all synthetic benchmark programs are very small. Not surprisingly AMD looks great on the latter and terrible on the former because the microarchitectural resources they've committed to branch prediction and speculation are meager and their weird memory architecture exacerbates the problem.
- kllrnohj 7y agoNonsense. Epyc's memory latency is only slightly behind Intel's, and every test other than MySQL shows neck & neck IPC across dozens of real-world programs that definitely don't fit in L1. POV-Ray doesn't fit in L1 and Epyc 7601 trivially bests the Xeon 8176, and does so while using a ton less power. Similarly NAMD, even with AVX & compiled with Intel's ICC, runs waaaay faster on Epyc 7601 than it does on Xeon 8176. Maybe your workload is exclusively MySQL or looks a lot like it. If so, sure, go buy Intel. But there's a ton of cases where there is no where close to such a gap, including large cloud workloads. You keep taking a single benchmark result and massively over-extrapolating it to mean the entire cloud hosting world. That's not how this works.
- BubRoss 7y agoYou seem to be very invested in disparaging AMD, but haven't provided any links to back up your claims, some of which are completely bizarre.