10 ms·
Ultimately it's the total cost to run your application that's important, not the raw speed of a particular core. Not necessarily. A core that's 1/3 the speed c
by wmf 8y ago
Ultimately it's the total cost to run your application that's important, not the raw speed of a particular core.
Not necessarily. A core that's 1/3 the speed can multiply your response time by 3x. https://static.googleusercontent.com/media/research.google.com/en//pubs/archive/36448.pdf https://static.googleusercontent.com/media/research.google.c...
- rbanffy 8y agoIt depends on how CPU-bound you are. If you spend a lot of time waiting for DRAM, disk or network, then you won't notice. It's a bit like answering e-mail on a Celeron Chromebook compared to your dual Xeon Platinum quad Nvidia desktop. You won't notice the difference. 90% of the time the only difference I notice between my light-and-slow laptop I use for meetups and conferences and my heavy-and-beefy one is that the puny one has no built-in fan. When running Python code, my very methodologically questionable benchmarks indicate the size of the L1 cache makes a huge difference, so I'll take an ARM64 box with a Core i9 worth of transistors used as cache over the i9 with an ARM64 worth of cache any time.
- reitzensteinm 8y agoDisk or network sure, but I don't think you can by any reasonable definition divorce "core performance" from the cache hierarchy and memory bandwidth that feeds it, at least in the context of the GP's post.