Hacker News Reader

Comment by hnuser123456 | Hacker News Reader

If anyone was confused like I was, it's (Xeon 7) (E-Core). It'll have 288 cores. The Diamond Rapids Xeon 7 P-core chip has 192 cores.

View on HN

This is more of a successor to the Xeon 6E (Xeon 6700E / Sierra Forest-SP), which had 144 cores. There was supposed to be a 288-core variant (presumably Xeon 6900E / Sierra Forest-AP), but they never released it to the public. I was looking forward to it since Sierra Forest-AP was supposed to support a 2-socket configuration (from motherboard spec). That's 576 physical cores in a single server!

The upcoming Zen6c will have 256 Core per socket, and dual socket gets you 512 Core. Since the Zen 6c support SMT while E-Core doesn't, the Zen6c would support 1024 vCPU in a single server!

I am looking forward to Zen6C vs Xeon 7-Ecore. Wondering about the cost / pref.

It's still mind-blowing to me to think that a decade earlier this would have been a few racks. Now it just fits within 1U or 2U. What an insane world we live in.

Indeed! Now with Up 2-4TB of Memory, and 1-2 PB of SSD. All inside 1-2U. By 2030 we will have server with 1000W CPU. We are fundamentally close to be limited by cooling.

And I forgot to include this. We have 1U of Server that could replace 1 Rack. That is 40x density increase. I wouldn't be surprised if we could increase this to 80x to 100x within another 10 years.

If that is the case, why do we need more DataCentre? Wouldn't it be easier to retrofit existing DC. Sometimes these sort of hyper scale is just so big they are beyond my imagination.

Sounds like a UltraSPARC-T1, all over again. A processor stuffed with efficiency cores for cloud loads.

Makes sense.

That did take me a beat. 7 cores? Must be pretty fast...

jealous of the person at Intel who gets to run `make -j 288`

Back in the day when Xeon Phi was around, I'd run `make -j 256` to run on the ~240 available hyperthreads. Those things were build machine beasts, assuming there weren't too many dependencies. For example. the Linux kernel would build files approximately ~240 at a time, which greatly sped up the build process, but linking was extremely slow (single-threaded on one very slow Phi core).

Even more interestingly, the Knights Landing series had a PCIe coprocessor version, which ran a stripped-down Linux kernel, and you could SSH onto it. One of my friends got one for free at a conference, and I really wish I'd picked one up!

Yes I had knl at some point . I tried it, tuned my code to work ok it, and since many optimizations carrried on to regular xeons … ended up buying Xeons.

Don't you get limited by memory bandwidth at that point? (assuming all disk contents are cached)

Is there _any_ confirmed information about Diamond Rapids, beyond one leaked (and seemingly slightly dubious) slide?

No, I don't think so.

maybe update the description

Intel's "Clearwater Forest" 288-core Xeon 7 CPU Will Be a Beast

Reply on news.ycombinator.com