6 ms·
48 Core ARM-64 processors from Cavium to challenge Xeons?
- valarauca1 12y agoThe biggest road bump for 48+ core SoC will be parallel programming. Because in truth nobody is (or at least doesn't want too). If you happened to be an early adopter of the SPARC T5 Niagra you likely noticed most of your utils ran very slowly. I just remember generating SSL keys at a speed that my pentium would laugh at, because SSL didn't supporting threading itself out to all 512 cores.
- pedrocr 12y agoI assume these kinds of chips are ideal for naturally parallel workloads like web servers. I wonder what the mWh/request looks like between one of these and a normal x86 server.
- bitL 12y agoAt SUN I was working with 256-thread SPARCs regularly and it was fairly simple to program using Java, except for some oddities in Solaris regarding networking stack. So if you need fast web servers, app servers or ETL, these chips can be pretty awesome. SPARC's threads were slower than ARM processors in mainstream phones nowadays, yet they were pretty good in handling web load. I would buy these chips in an instant, similarly to Parallela's 64-core ARM. The competition would be Xeon Phi - I assume that is much more expensive and the memory is too limited (8GB).
- 4ad 12y ago> Parallela's 64-core ARM Parallela is not a 64-core ARM, it's a 2-core ARM with a bunch of co-processors which have to be programmed specially. The co-processors have little local memory and the memory model is very weak, there are no memory barriers precluding the use of general-purpose code.
- Nursie 12y agoErrr, some of us have been in the business of writing parallelised code for quite some time now. A lot of enterprise* server stuff is written to take advantage of multiple cores/hardware threads and has been for a while. (*yeah, I hate that word)
- TillE 12y agoI've written a fairly wide variety of multithreaded code in the past ten years or so, and I think the only real trouble I've had is with algorithms that work step by step, each step dependent on the previous results. That's effectively impossible to parallelize without fundamentally changing the algorithm. Otherwise, even if you have large chunks of shared memory, it's usually possible to work around that without locks.
- mnw21cam 12y ago> The biggest road bump for 48+ core SoC will be parallel programming. And if you're okay with parallel programming (which, let's face it, is the only way to do high performance computing), then you'll possibly be hit by memory bandwidth or cache size. Because if you have 48 cores on a single lump of silicon, they won't have very large dedicated caches each. However, if you have an appropriate job that will scale out to all the cores with a small working set then the performance of this thing could be rather interesting.
- 4ad 12y agoThese chips are designed for networking equipment, not general purpose code. I don't understand how come the article fails to make this explicitly clear. Networking code has no problem with this high core count mostly because it was already written to work on already high-core count MIPS systems. For example, the previous MIPS64 offerings from Cavium pack 48 cores on a chip...
- jsnell 12y agoWhy do you claim that these chips are designed for networking? The article isn't just omitting the target market like you imply, but is very clear about Cavium targeting servers rather than just networking appliances. (I'm a lot pessimistic than most of the people in this thread. Network processors haven't really made a lot of sense compared to Xeons even for networking applications for a few years. Why would they do any better in the general purpose market?)
- windexh8er 12y agoThey are not just designed for networking, but the bulk of their customers are: A10, F5, Sonicwall, Cisco, Juniper, Palo Alto Networks (http://www.cavium.com/winning_products.html http://www.cavium.com/winning_products.html) "...haven't really made a lot of sense..." - You are completely wrong here. Most data center grade networking equipment does not run Xeon and the products that do are generally significantly less performant. Especially when it comes to security or packet inspection.
- kjs3 12y agoIf you narrow the statement down to "the highest performance network gear don't use Xeons", I suppose you get to be right. Almost all of my data-center security and packet inspection devices have a Xeon or two in them. The Cisco ASAs, Fireeye APT probes, Imperva WAFs, F5 load balancers, Sourcefire IDS. A couple of them also have packet processing support hardware (Endace cards, mostly), but that's mostly for taking the packet processing off the Xeons and letting them do just the inspection. But hey, we're only doing a couple of gig sustained, so we aren't the cool kids.
- rbanffy 12y agoNiagara was too much ahead of its time. And a crypto accelerator would have been helpful (even if shared by a group of cores). I imagine memory bandwidth will become a problem as soon as we start designing our software to branch out enough threads to feed all the 48 mouths of this chip, but, still, this is how things will be in the future so it'd be wise to start designing for it right now.
- hapless 12y agoNiagara included a crypto accelerator. Its successor chips had fancier ones. https://blogs.oracle.com/ningsun/entry/cryptography_acceleration_on_ultrasparc_t2 https://blogs.oracle.com/ningsun/entry/cryptography_accelera...
- deleted 12y ago[deleted]
- signa11 12y agotilera ?
- joosters 12y agoWhen you have tens of CPU cores, you really do start to run up against Amdahl's Law and soon don't get the speedup that you might expect. e.g. let's say 90% of your task can be perfectly parallelised. The remaining 10% of the time will not be improved. So you won't ever get more than a 10x speedup no matter how many tens or hundreds of extra CPU cores you have...
- xienze 12y agoWell, you're thinking in terms of parallelising a single task. For a server, you're talking about a large number of concurrent tasks (users), so more cores are better in that case.
- joosters 12y agoThat's basically a truism. If you have parallelisable tasks, then they will parallelise. No surprise there. I was trying to make the point that as we step up the number of cores, the actual gain is less and less.
- deleted 12y ago[deleted]
- rbanffy 12y agoAgain, as it was pointed out earlier, no. If you have 48 runnable threads from 48 different tasks running on your machine, you'll get pretty much linear performance increases (memory bottleneck excepted). It's not a processor designed to run Office or Firefox, but it may be very interesting on a server or as a competitor for the Xeon Phi. BTW, considering even my humble laptop can do 8 threads at once, it's about time we started building office suites and browsers to take advantage of these processors.
- jallmann 12y ago> If you have 48 runnable threads from 48 different tasks running on your machine, you'll get pretty much linear performance increases Only if the tasks are trivially parallelizable. Any sequential dependencies among those tasks limit the effectiveness of parallelization. This is exactly what Amdahl's Law says. > my humble laptop can do 8 threads at once, it's about time we started building office suites and browsers to take advantage of these processors. Multiple browser tabs or open office documents are trivially parallelizable (eg, processes). The work within those tabs or documents is not linearly parallelizable -- running JS/macros, handling input, rendering, etc. Existing browser/office suites already do a pretty good job of splitting these tasks up, but they can't be split up arbitrarily into $core_count chunks.
- rektide 12y agoCavium announced a 48 x 64-bit chip running 2.5GHz almost two and a half years ago: the Octeon III. http://www.cavium.com/newsevents_Cavium_Unveils_48-core_OCTEON-III_MIPS64_Processor.html http://www.cavium.com/newsevents_Cavium_Unveils_48-core_OCTE...
- personZ 12y agoWorth noting that Intel already has a many weaker core design -- the Xeon Phi. While it exists as an add-in "co-processor" right now, in 2015 it will become a stand-alone platform via Knights Landing.
- bitL 12y agoXeon Phi seems to be targeting two markets at once - many-core (x64) server computing and GPGPU with their 512-bit SIMD. For general server the memory limitation to 8GB is too low, which is however very competitive in GPGPU market.
- personZ 12y agoTheir new models are 16GB, but you are exactly right that the model is very similar to the GPGPU (less memory, but what it does have is incredibly fast), albeit fewer but higher performance cores than something like a Tesla. Knights Landing is when the model becomes a server unto itself, with 384GB of addressable memory, albeit still maintaining the ultra-fast 16GB of local memory per CPU.
- bitL 12y agoExciting times ahead ;-) Also, there is a difference in required memory architecture when it comes to optimizing CPU thread performance vs SIMD - CPU is more sensitive to latency, SIMD to bandwidth. You usually have to pick the memory type (e.g. DDR3 vs GDDR5) that optimizes one of those and that would tell you what market you target. I am not sure how AMD handles their HSA - they seem to have discontinued plans for GDDR5 so their Fusion GPU is going to be bandwidth-starved.
- hapless 12y agoThe chip is vaporware. They've been talking about it for two years, but to quote the article, "Cavium has yet to share performance figures for the chip, which is not yet in first silicon." I will be very excited to see some hard numbers when (if) this thing is ever released.
- windexh8er 12y agoHaving been looking for some ARMHF images for Ubuntu I stubled across this. Looks like Ubuntu is all over this (as well as RHEL including Fedora, and Monta Vista: http://www.ubuntu.com/download/server/arm http://www.ubuntu.com/download/server/arm Links to "Project Thunder SDK": http://www.cavium.com/thundersdk_access_application.html http://www.cavium.com/thundersdk_access_application.html
- kjs3 12y agoWonder why Cavium jumped from MIPS to ARM for this? At least, all the Cavium kit I have is MIPS based.