HIGH PERFORMANCE COMPUTING
“Existing simulation codes are not expected to be able to fully exploit the next generation of supercomputers”
work with them to demonstrate that the programmability yields a significant benefit of some kind. For example, it might enable a new kind of highly optimised collective communication operation, which might mean that some codes are able to go a lot faster. If we can’t think of a really good use case and get a significant benefit from that new feature, then maybe that was interesting to try, but it’s not going to revolutionise what we’re doing in the future. In each case, we’re looking for a route to a significant benefit from a new technology for exascale computing and exascale science codes in the UK. That’s ultimately what it comes down to. For FPGAs, if they could get you a 10 times speed up, but you’ve got to rewrite all your code into register transfer language (RTL) and you’re basically generating hardware, that’s probably a non-starter. For new kinds of processors, it is especially important to evaluate ease of use. So on an FPGA, you can now actually write code in a high-level language that you might want to use anyway – for
www.scientific-computing.com | @scwmagazine
example, there are some people looking at whether you can use SYCL, which is a sort of high level C++ parallel abstraction, which you can also use with GPUs and multi-core CPUs. If you could use an approach like SYCL
and from that generate efficient code for FPGAs, as well as CPUs and GPUs, that would be powerful. But if you have to rewrite all your code for a specific platform, that’s probably not going to happen. Ease of use and ease porting are key metrics in any kind of new technology we’re considering within ExCALIBUR.
Are there any early success stories from these early evaluations of new hardware? We have got some FPGAs in the ‘Hardware and Enabling Software’ program, but those are some of the more recent projects that are starting up. We have some projects evaluating the Bluefield technology from Mellanox, now Nvidia, and that’s been useful to get a feel for what these programmable network technologies can and can’t do. We’ve had several projects evaluating
different kinds of GPUs. Over the last 10 years, Nvidia has owned most of the GPU market in HPC, but other GPUs are becoming important now too. AMD GPUs in particular are being used in many of the first wave of exascale machines in the USA. Intel has some exciting GPU technology coming to HPC soon in the
form of their Ponte Vecchio GPUs. We’ve had a couple of projects looking at AMD GPUs, and getting things running on those as well as Nvidia GPUs, and that’s been quite successful. We’ll evaluate Intel’s Ponte Vecchio GPUs when they become available too. These efforts will ensure we have much more agility in UK science codes so they can use any of the technologies in the future when they turn out to be successful. This means we need UK science codes
to run on whichever GPUs turn out to give us the most science per pound, whether those are AMD, Intel or Nvidia GPUs, and ideally, our codes will be able to run well on all of them. This is a key goal ExCALIBUR is trying to achieve. We have got some of the AI and machine learning hardware available to the project as well. For example, we have some of the Graphcore technologies available both in Bristol and at UCL. This is a nice story because the Graphcore processor was designed here in Bristol, so it’s good to have a local link there. We also have the Cerebras technology, which is from the US. One of these systems has recently been installed in Edinburgh as part of the ExCALIBUR hardware and enabling software programme. This is one of the first of its kind anywhere in the world, so it’s quite exciting to be able to make these new technologies available to AI and machine learning users in the UK.
Autumn 2021 Scientific Computing World 11
Gorodenkoff/
Shutterstock.com
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34
