Thank AMD for not giving importance to niche areas in their first attempt back at competitiveness.Blame me for AMD's poor AVX2 implementation.
What if I want a 2P 56 core system? Or even a single 28C workstation? Surely Platinums being capable of 8p doesn't mean that that's the only configuration they're capable of running.
So 12% from IPC and 25% from clock advantage is final word in ST performance? Sounds fine to me. 40% is not too shabby of advantage.
So what's better value - 18C Gold @3.7GHz all cores, or 24C Platinum @2.8GHz all cores?And what is keeping You from it? Your original question compared Gold vs Platinum, and I answered why Platinum exists even if it's performance seem the same and is priced as-is: RAS and 8C. If all you need is 1S, you can freely stuff 28C in here, the rest of us will look into value and maybe go with 1S 20C or 2s 16C or whatever is required?
So what's better value - 18C Gold @3.7GHz all cores, or 24C Platinum @2.8GHz all cores?
What do you want to here exactly? No, better ST performance will not always replace more cores, as more cores will not always replace better ST performance. It is very much task dependent.So what's better value - 18C Gold @3.7GHz all cores, or 24C Platinum @2.8GHz all cores?
Also, if according to you, cache, TDP, clocks, platform, multi-socket scalability, etc. are all reasons why frequency*core count isn't a good indicator of MT performance, then why is just a simple 40%(IPC+clock) increase an absolutely valid indicator of ST performance?
RAS is available across the board.Nice try. And the answer is none of them unless you are bound by some sort of strict SLA. If one needs predictable 3.7Ghz perf you go with Gold, if you need RAS you go with Platinum. Otherwise you go with some some other Gold (or even Silver) cpu that has better perf/$ and enough capacity. Easy as that.
But let's leave Xeon alone, that is a topic only head devil in Intel's marketing can answer.
Then why the circlejerk around OC'd 8700K Cinebench MT scores implying a certain slower 8C/16T CPU would become irrelevant?(not that it's you specifically who's making such claims)What do you want to here exactly? No, better ST performance will not always replace more cores, as more cores will not always replace better ST performance. It is very much task dependent.
Same thing can be said about programs and core scaling - some of them don't, a lot of them do.Yes, not every program scales with lakes' clock speeds but it seems a lot of them do.
Agreed. The problem is that everyone wants the last word in these kind of debates and before you know it, the thread has 5 pages of off topic discussion. I am partly guilty of this as well. Now can we seriously get back on topic and discuss Coffee Lake? I didn't come here to read about Xeons. Thank you very muchBetter yet, could we get on topic? Could someone make a "More cores vs. ST performance" thread already?
If one of CPUs is executing same 256bit vector workload in half of the time and program instruction count to retire is const, wouldn't the faster CPU have double IPC?
If one of CPUs is executing same 256bit vector workload in half of the time and program instruction count to retire is const, wouldn't the faster CPU have double IPC?
This, let's call it STPC and be done with it!IPC is such a bad term. What people really are talking about is single threaded performance per clock.
It has been shown again and again that the IPC difference is like 8-10 percent, not 10-20 percent. Gaming performance isn't a measure of IPC. Performance scaling with frequency isn't linear for all but canned benchmarks like Cinebench. So 30 percent improvement is for situations with ideal ST scaling.
Because the clock frequency within a CPU is a reference of time. Cycles refer to periodicity of the waveform of the clock signal. If some instruction takes two cycles to execute, then it will still take two cycles to execute whether the CPU is at stock or overclocked.
I'll just cite Agner Fog's Instruction Table.But we are not talking about frequency here as in Hertz which is cycles per second and the clock in the CPU used for execution is not used as a reference of time.
Examples from Intel optimization paper https://software.intel.com/sites/default/files/pentium-processor-optimization.pdf
Can you see per cycle in the description is the per clock in the expression.
![]()
Can you see counting clocks is the same as counting cycles
![]()
Or we can take the reciprocal CPI
![]()
Latency:
The latency of an instruction is the delay that the instruction generates in a dependency chain. The measurement unit is clock cycles.
Reciprocal throughput:
The throughput is the maximum number of instructions of the same kind that can be executed per clock cycle when the operands of each instruction are independent of the preceding instructions. The values listed are the reciprocals of the throughputs, i.e. the average number of clock cycles per instruction when the instructions are not part of a limiting dependency chain. For example, a reciprocal throughput of 2 for FMUL means that a new FMUL instruction can start executing 2 clock cycles after a previous FMUL. A reciprocal throughput of 0.33 for ADD means that the execution units can handle 3 integer additions per clock cycle.
I'll just cite Agner Fog's Instruction Table.
Why didn't you respond to the person I was responding to as well, if you find these digressions irrelevant? Can't believe people have this much trouble finding relevant information on the internet in this day and age.I know it's difficult for you, but would you please refrain from gumming up this thread any further? It's getting old having to skim through post after post to try to find Coffee Lake specific information.
AVX512 isn't supported.Talking about AVX, is it fully supported in KabyLake/CoffeeLake just like in Skylake-X?
Why didn't you respond to the person I was responding to as well, if you find these digressions irrelevant? Can't believe people have this much trouble finding relevant information on the internet in this day and age.
ah ok, I guess that explains some video encodng bench Ive seen, where SK-X is clearly faster than Coffee, despite its lower freq clockAVX512 isn't supported.