wow this is incredibly SHITTY, no matter how you spin it, at the tech level it's terribly bad, letme expand:
first you have a non-monolithic-ish CPU design -not quite MCM but you could call it "MCM on die"- that communicates with each other on a 256bit bus as well as the other uncore parts with a crossbar configuration, that by tiself already kills your performance as the inter CCX comm use this slow-ass bus, as pc perspective benchmarks showed it wreaks havoc on cache coherency and L3 access beyond local cache(intel does not have this issue).
And then you compound that by tying the bus to EXTERNAL RAM speed by making the memory controllers the "bus master" essentially, that's beyond bad design, it's appallingly bad
Intel with their Xeon HCC(high core count) does something similar as their ring bus max at 16 cores, so for 22 cores it has 2 ring busses that connect to eachother with bus bridges that have a very small impact of performance and each ring has a dedicated memory controller, in BIOS you can enable "cluster on die" mode which turns the single chip(it's still a monolithic core) into a numa-node for performance reasons(to stop the right ring from acesing the left rin ram space over the bridges), THAT is what you call an elegant and sophisticated design, the ring bus does not depend on the RAM nor core clocks
on one hand, AMD touts ryzen as the expensive intel killer... but they need to most expensive un-buyable memory to actually perform better?, top kek there AMD...
so Intel has not only a very big IPC lead with KBL, but they can maintain that IPC regardless of whatever shitty cheap ram you throw into the system.
Also remember that this is going into naples, and server ECC RDIMM memory tops at 2400, plus massive fabric overhead, as naples will be a MCM(mayeb even interposer to route the massive 256 bit bus) of 4 ryzen dies, each die provides 2 channels of ram so inter-chip ram/cache will be slow as molasses.