Last week AMD pre-announced its next-generation EPYC processors, code-named Rome. These new processors are set to be officially announced next year, but will feature up to 64 cores using eight 7nm chiplets surrounding a central 14nm IO die. This week is the annual Supercomputing conference, focusing on high-performance computing, where all the big OEMs with server offerings as well as supercomputing centers get to promote their latest and greatest. One of them is the High Performance Computing Center based in Stuttgart, Germany, who disclosed some information about their new ‘Hawk’ system.

Supercomputers are measured in many metrics: processor type, cores, power, peak throughput, peak performance, interconnect, memory, and many others. The first supercomputer disclosed to be using AMD’s upcoming EPYC Rome processors is ‘Hawk’, based at HLRS, and set to be installed in 2019. The base systems will be developed by HPE, listed as HPE’s ‘Badger’ portfolio.

Details for Hawk were given by the HLRS Director, Prof. Michael Resch, at a talk at the AMD booth here at Supercomputing. The title of the talk was given as ‘AMD in a Large Scale Computing System for Science and Industry’, with a focus on HLRS as a local driving force for compute as well as the work it does. The requirements for the new Hawk system were listed as high performance, professional support/collaboration, lowest possible TCO, and high level of sustainability.

The key slide for us in the talk is this one.

The slide has EPYC misspelled in it, as it is misspelled in a number of places in the slide deck, along with other mistakes – the speaker’s first language is not English.

The slide describes Hawk as a 640,000 core system using 64-core Rome CPUs. That’s 10000 CPUs, listed at a throughput of 24.06 PetaFLOPs. That gives 2.4 TeraFLOPS per CPU, which at 16 SP flops/cycle, works out about correct for a 64 core CPU for the 2.35 GHz frequency mentioned in the slide. This would appear to be a base frequency, although AMD’s Naples processors do offer a ‘constant frequency’ mode to ensure consistent performance. Main memory was listed as 665 TB, with 26 PB of disk space. It was not disclosed the breakdown of how the disk is split between NAND and HDDs.

Unfortunately Prof. Resch was not available for additional questions.

Related Reading

Comments Locked


View All Comments

  • deil - Wednesday, November 14, 2018 - link

    build like that deserve EPIC instead of EPYC :)
  • tommo1982 - Wednesday, November 14, 2018 - link

    I, by no means, am an expert, but I assume the new chiplet design with separate I/O chip must be pretty good to end up in a supercomputer. It's interesting to see how AMD is slowly gaining a foothold in server space, again.
  • don03 - Wednesday, November 14, 2018 - link

    But can it play Crysis?
  • warumich - Wednesday, November 14, 2018 - link

    With huge explosions, it maxes out the 64 000 CPU cores, but overall, i would call it playable.
  • schujj07 - Wednesday, November 14, 2018 - link

    At 2.4 TeraFLOPS per CPU that works out to 37.5 GigaFLOPS per core at 2.35GHz. How does that compare to Zen+ or Coffee Lake?
  • efferz - Wednesday, November 14, 2018 - link

    I remember that the FMA instructions provide 2x fp performance,so it should be 4.8TFlops per CPU
  • DeepLearner - Wednesday, November 14, 2018 - link

    That's a disappointing frequency increase, even with the extra cores.
  • EasyListening - Thursday, November 15, 2018 - link

    safety first
  • BurntMyBacon - Monday, November 19, 2018 - link

    I would not assume that is all that the processor is capable of. More likely, that is the base clock. That said, this system may be running fix frequency so as create consistent power draw and thermals. This prevents them from over spending (money and/or space) on power distribution and cooling.

Log in

Don't have an account? Sign up now