in High Performance Computing Victor Eijkhout CppCon 2024 Introduction This poster reports on ‘D2D’, a benchmark that explores elegance of expression and perfor- mance in the context of a High Performance profiling and discussion of performance. By presentation time: So far, exclusively top-of-the-line high core count processors were used. I will compare to a more ordinary desktop, where bandwidth limitations

Introduction Firsts steps Context Theoretical foundations Outline of an implementation Conclusion High-Performance Numerical Integration in the Age of C++26 Vincent Reverdy Laboratoire d’Annecy de Physique Verner’s methods Explicit adaptive Runge-Kutta schemes Slightly enhanced methods with interpolants High-accurary interpolation inside integration steps Interpolation with extra coefficients βi yn+u = talk of last year for the implementation of this kind of expression templates: Symbolic Calculus for High-Performance Computing from Scratch using C++23, V. Reverdy, CppCon2023 CppCon - Vincent Reverdy -

Comparison Binding Constraints Architecture Substitution Construction Conclusion Symbolic Calculus for High-Performance Computing from Scratch using C++23 Vincent Reverdy Laboratoire d’Annecy de Physique . What this talk is not about Complicated maths (you are smart people, you can do it yourself) High-performance computing (you all know about it + see the 2019 talk for that) Benchmarks, assembly, mathematical concepts Symbolic calculus (derivatives, integrals) Full blown custom rule-based rewriting High-performance Since formulas have the entire information on the mathematical AST, it’s possible to

to, different servers (“remotes”), similar to the “git” push-pull model to/from git remotes. On a high level, the servers are just package storage. They do not build nor create the packages. The packages on-premises server. It is a more powerful solution, featuring a WebUI, multiple auth protocols, High Availability, etc. It also has cloud offerings that will allow you to have private packages without having (either True or False) indicates whether SSL should be used to verify that remote. The local cache registry.txt file contains the remotes definitions, as well as the mapping from packages to remotes. In general

to, different servers (“remotes”), similar to the “git” push-pull model to/from git remotes. On a high level, the servers are just package storage. They do not build nor create the packages. The packages on-premises server. It is a more powerful solution, featuring a WebUI, multiple auth protocols, High Availability, etc. It also has cloud offerings that will allow you to have private packages without having in the registry.txt/registry.json files and they provide a helpful starting point when writing the remotes.txt to be packaged in a Conan client configuration. Important: The local cache registry.txt/registry

to, different servers (“remotes”), similar to the “git” push-pull model to/from git remotes. On a high level, the servers are just package storage. They do not build nor create the packages. The packages on-premises server. It is a more powerful solution, featuring a WebUI, multiple auth protocols, High Availability, etc. It also has cloud offerings that will allow you to have private packages without having (either True or False) indicates whether SSL should be used to verify that remote. The local cache registry.txt file contains the remotes definitions, as well as the mapping from packages to remotes. In general

to, different servers (“remotes”), similar to the “git” push-pull model to/from git remotes. On a high level, the servers are just package storage. They do not build nor create the packages. The packages on-premises server. It is a more powerful solution, featuring a WebUI, multiple auth protocols, High Availability, etc. It also has cloud offerings that will allow you to have private packages without having in the registry.txt/registry.json files and they provide a helpful starting point when writing the remotes.txt to be packaged in a Conan client configuration. Important: The local cache registry.txt/registry

to, different servers (“remotes”), similar to the “git” push-pull model to/from git remotes. On a high level, the servers are just package storage. They do not build nor create the packages. The packages on-premises server. It is a more powerful solution, featuring a WebUI, multiple auth protocols, High Availability, etc. It also has cloud offerings that will allow you to have private packages without having (either True or False) indicates whether SSL should be used to verify that remote. The local cache registry.txt file contains the remotes definitions, as well as the mapping from packages to remotes. In general

to, different servers (“remotes”), similar to the “git” push-pull model to/from git remotes. On a high level, the servers are just package storage. They do not build nor create the packages. The packages on-premises server. It is a more powerful solution, featuring a WebUI, multiple auth protocols, High Availability, etc. It also has cloud offerings that will allow you to have private packages without having in the registry.txt/registry.json files and they provide a helpful starting point when writing the remotes.txt to be packaged in a Conan client configuration. Important: The local cache registry.txt/registry