Ampere unveils monstrous 512-core AmpereOne Aurora processor — custom AI engine, support for HBM memory

asdf
(Image credit: Ampere)

Ampere is adding the new 512-core AmpereOne Aurora processor to its roadmap, the company announced today. This new chip has custom Arm cores and a custom mesh and die-to-die interconnect. It also supports HBM memory and Ampere's next-gen AI acceleration blocks, but the company hasn't yet announced the specific launch timing. 

Ampere also unveiled pricing for its AmpereOne M processors, with the flagship 192-core model weighing in at $5,555, and outlined progress with its AmpereOne MX processors, which stretch up to 256 cores on the TSMC 3nm process node. Lastly, the company also provided deep-dive details for its AmpereOne architecture and shared more performance claims and benchmarks.

Latest Videos FromTom's Hardware
Paul Alcorn
Editor-in-Chief

Paul Alcorn is the Editor-in-Chief for Tom's Hardware US. He also writes news and reviews on CPUs, storage, and enterprise hardware.

  • JRStern
    Somebody tell me please, what do people *do* with all these cores, ARM or x86? Do they not overload memory and IO channels?
    Reply
  • bit_user
    Eh, they're comparing against CPUs already a couple years old, but I think it will mostly have to compete with Zen 5 EPYCs, not to mention Sierra Forest:

    Don't get me wrong: I'm glad there's someone building server-grade ARM CPUs you can actually buy and run as a "SOHO" user. I'm mainly skeptical of their approach in using a custom core design (again), but I suppose they can always go back to licensing ARM's Neoverse cores.

    Also, I didn't see mention of SVE, which I think is lamentable. Now that Nvidia has SVE2 in Grace and Amazon has it in their Graviton 4, it looks like the ARM server market might finally be transitioning to it.
    Reply
  • zanessepp
    JRStern said:
    Somebody tell me please, what do people *do* with all these cores, ARM or x86? Do they not overload memory and IO channels?
    I've seen mentions of using these as front-end reverse proxy servers where you do need to process a bit of data, but all of the heavy lifting is dispatched to backend app services. For large services I can see the benefit, but I've not seen any benchmarks.
    Reply