Qualcomm Launches 48-core Centriq for $1995: Arm Servers for Cloud Native Applications
Following on from the SoC disclosure at Hot Chips, Qualcomm has this week announced the formal launch of its new Centriq 2400 family of Arm-based SoCs for cloud applications. The top processor is a 48-core, Arm v8-compliant design made using Samsung's 10LPE FinFET process, with 18 billion transistors in a 398mm2 design. The cores are 64-bit only, and are grouped into duplexes – pairs of cores with a shared 512KB of L2 cache, and the top end design will also have 60 MB of L3 cache. The full design has 6 channels of DDR4 (Supporting up to 768 GB) with 32 PCIe Gen 3.0 lanes, support for Arm Trustzone, and all within a TDP of 120W and for $1995.
We covered the design of Centriq extensively in our Hot Chips overview, including the microarchitecture, security and new power features. What we didn't know were the exact configurations, L3 cache sizes, and a few other minor details. One key metric that semiconductor professionals are interested in is the confirmation of using Samsung's 10LPE process, which Qualcomm states gave them 18 billion transistors in a 398mm2 die (45.2MTr/mm2). This was compared to Intel's Skylake XCC chip on 14nm (37.5MTr/mm2, from an Intel talk), but we should also add in Huawei's Kirin 970 on TSMC 10nm (55MTr/mm2).
Previously: Qualcomm's Centriq 2400 Demoed: A 48-Core ARM SoC for Servers
(Score: 4, Insightful) by bob_super on Thursday November 16 2017, @01:47AM (10 children)
They run at over 2GHz, decently priced for that market.
As more and more tools get ported to ARM, and more and more people realize that their phones are running apps quite competently on ARM, Intel is potentially going to get a run for its money on the desktop too.
That's an interesting development, after all those years of cheering for all the much better architectures, which got crushed by x86 for lack of SW support...
(Score: 3, Interesting) by takyon on Thursday November 16 2017, @01:51AM
Epyc 2 (AMD x86 Ryzen for servers) could ship with 64 cores.
https://hothardware.com/news/amd-epyc-2-64-cores-128-threads-and-256mb-l3-cache [hothardware.com]
[SIG] 10/28/2017: Soylent Upgrade v14 [soylentnews.org]
(Score: 2) by c0lo on Thursday November 16 2017, @02:38AM (5 children)
The "we should also add in Huawei's Kirin 970 on TSMC 10nm" at the end of TFS.
Made me curious and I got this [digitaltrends.com]:
- the designer - Huawei [wikipedia.org] - Chinese. Largest telecommunications equipment manufacturer in the world.
- the foundry - TMSC [wikipedia.org] - Chinese. Largest dedicated independent semiconductor foundry
Ooopsie. Mandarin, do you speak it...?
https://www.youtube.com/watch?v=aoFiw2jMy-0 https://soylentnews.org/~MichaelDavidCrawford
(Score: 2) by takyon on Thursday November 16 2017, @02:47AM (4 children)
1. TSMC, not TMSC. It's a mistake many have made, including me.
2. TSMC is Taiwanese rather than Chinese. A distinction that might help you avoid getting beat up by a Taiwanese nationalist.
[SIG] 10/28/2017: Soylent Upgrade v14 [soylentnews.org]
(Score: 2) by c0lo on Thursday November 16 2017, @03:40AM
Mmm... the "for now" qualifier seems needed.
Uhhh... again a matter of choice, being beaten by a Taiwanese nationalist or facing jail in the mainland China [thediplomat.com]?
'Cause the latter is quite strong-minded [thediplomat.com] in regards with the "one country, two systems".
https://www.youtube.com/watch?v=aoFiw2jMy-0 https://soylentnews.org/~MichaelDavidCrawford
(Score: 1, Disagree) by WillR on Thursday November 16 2017, @03:16PM (2 children)
...where they speak Cantonese. Now you have two languages to learn.
(Score: 2) by bob_super on Thursday November 16 2017, @05:28PM (1 child)
That Mandarin- and Taiwanese-speaking Taiwanese nationalist is very disappointed, though not entirely surprised, at your ignorance.
(Score: 1) by WillR on Friday November 17 2017, @10:27PM
(Score: 2) by JoeMerchant on Thursday November 16 2017, @03:47AM (2 children)
So, this doesn't seem to compare well with a rack full of Raspberry Pis - granted there are plenty of applications that will run better on the Qualcomm configuration, but if you're looking at flops per dollar, or fault tolerance, it would seem like a re-spin of the basic Raspberry Pi concept (but with a respectable GHz network connection this time) could get you there with just a slightly larger equipment rack.
🌻🌻 [google.com]
(Score: 4, Insightful) by TheRaven on Thursday November 16 2017, @09:19AM (1 child)
sudo mod me up
(Score: 3, Interesting) by JoeMerchant on Thursday November 16 2017, @12:43PM
As I mentioned, the Pi's I/O is lame - but the basic approach of a rack full of inexpensive ARM systems would still seem to address a lot of needs, even and perhaps especially cloud needs without resorting to the BIG IRON.
IBM tried making BIG IRON systems for the cloud about 10 years ago (ahead of their time, right?) Their pitch was to create an (apparently) "overpowered" system which they would divvy up with hypervisor and then lease you the capacity you needed out of it. The appeal was supposed to be that the hardware would "scale" with demand and you only paid for what you used.
We did an analysis of those IBM systems vs a rack of Mac Pros, and, in the end, if you were really using all the capacity of the system, the IBM was coming in at roughly 25% of the flops per dollar of dedicated Intel cores.
So much cloud is just a stone simple app accessing a tiny sliver of data, scaled up to many users accessing many different slivers of data - things that one Pi could probably service many many active users simultaneously without a struggle. Instead of scaling by having a massively powerful chip that you slice up into thousands of services, the approach of having a modest unit that you replicate thousands of times gives you the ability to match capacity to need much more closely.
Of course, the sales appeal is: I can't predict my need, it could be MASSIVE - to which the BIG IRON sellers reply "don't worry, we've got you covered." But a system of many little workers doing many little jobs can scale up too. Have you ever seen a sweatshop full of laborers? There's many good reasons businesses use that model, and CPUs don't need healthcare coverage.
🌻🌻 [google.com]