sry all for continually going off topic
There is no point comparing datacentre to server cost, Datacentres have ROI periods of upto decades , servers/storage have 3 years, networking and storage networking normally around 5 years sometimes upto 10. But if we look at a standard 2P server using iSCSI or FC for storage. The best value for money memory is 16gb rdimms, on a 2P box with intel that's 384gb. to go to 32gb rldimm's(768) is about 20% more per gb then 16gb, to go to 64gb rldimm(1536) is about 60% more per gb vs 16gb. Now if you are using 22 core E5's memory makes up 30%/50%/70% of the platforms cost. But dropping to 16-18 core CPU cuts CPU cost in half, this where most bulk VM farms sit in terms of CPU spec. With this spec your 384gb is now taking closer to 50% platform cost. This is what a standard VM farm server looks like. On average these servers are memory throughput and memory capacity limited.
Now with Zen, You could hit something like 18-24core a socket CPU with up 512gb of memory with 16gb dimms because you are generally memory capacity/performance limited. So assuming 18cores a proc you end up with Xeon giving you 5gb of memory a thread vs 7gb of memory a thread for Zen. assuming both run DDR4 2400 its also around 25-30% more memory throughput per thread. Where this really starts to play out is with over subscription/ballooning policies, You can over subscribe CPU massively as you are always memory or io limited, the second your memory limited or your hypervisor pages to disk its all over entire server is in the toilet.
This is flat out wrong, go look how a standard virtual server is sold, go look and what the average usage profile of a common enterprise application looks like (end to end dev,QA,pre-prod,prod). If you think a 10% perf per clock matters to all but niche area's you just don't understand what matters. Repeat after me, VM density is what drives the vast majority of server sales. Think about that, comprehend that.
Your own cognitive bias is getting in the way of basic interpretation skills.
1. The ball park spilt ball figure based off one data point as being 10% behind was 8core Zen to 8 core broadwell.
2. The next Xeon's aren't coming soon they are already out, 28core is the SOC size, not what you can buy
3. because of the small (~200mm sized zeppelins) on MCM they can mix and match different yielding chips and actually sell full sized SKU's
4 Next go look at the costs to buy the high end SKU, your just showing your ignorance, those 28core chips are going into boxes that have software with high per socket licencing costs Not the servers that make up 90% of server sales.
5. Your ignoring at a minimum the SOC level features not yet in broadwell, you know the things the big guys ask for in Xeon-D that are in Zen.....
6. Consider the price that P10 is sold at now consider that a Zeppelin die is likely smaller on the same node,
7. Servers don't need the high frequency scaling the need low power in the 2ghz to low 3ghz range, this largely mutes the DERP DERP mobile process issue because that's exactly where mobile processors sit.
8. You completely ignore the comments about the 32core product looking really good.... shock horror surprise!
Yes and then lets look at jaguar, but that doesn't agree with your position so lets ignore that data point......
So you bring up bulldozer so lets compare bulldozer to Zen .
Bulldozer:
From the very first benchmark bulldozer looked bad
Bulldozer has issues with L1i associativity
Bulldozer had much smaller PRF/LS queue/Retirement queue per core then sandy bridge
Bulldozer had the horrible L1D/L2/WCC latency thing going on
Bulldozer was so ALU bottlenecked they moved some ALU instructions to the AGU
Bulldozer had long load to use latency for FPU and slow FPU execution for non FMA (SSE etc)
Bulldozer had lots of functions on few execution ports (branch and mul on same port)
Bulldozer * lots of other stuff see agnar,
http://blog.stuffedcow.net/2014/01/x86-memory-disambiguation/ etc
Zen:
First benchmarks ( we only have geekbench4 on the 2P 32 core part which is 10% behind in ST clock for clock to E5 22 core part and the blender example) look good
First hand accounts from people known to work for OEM's saying that both ends of the Zeppelin spectrum look good ( 8 core and 32 core)
Zen has better L1i associativity then bulldozer comparable to Intel
Zen has broadwell to skylake sized internal data structures
Zen has a far more traditional cache structure and no Write Though L1D
Zen has as much integer execution resources as >=Haswell
Zen has multiple of all integer ops ports and can do two branches in a cycle
Zen has reduced load to use latency for FPU and lower execution latency for the FPU
The issues Bulldozer had where all around its target design and ultimately the target design was wrong, don't confuse target design with capability of individual components.
I have no idea where Zen performance will actually fall, but right now with all that we know from linkdin, compiler patch notes, AMD presentations, CERN leak etc all point towards a competitive micro architecture and a competitive at least in 1P platform configuration, I really hope for AMD 2P isn't an issue for NUMA aware independent workload stuff ( you know VM's all hyper visors are NUMA aware) given that we have been told there are 2P issues.
You have done nothing but hand waving and DERP DERP AMD.
So put your money where your mouth is what are the issues with Zen, Why would 10% perf per core matter ( be specific).