prototypes and early research.Problem: writing parallel programs is hard - Multi-GPU, multi-CPU systems require partitioning data - Users must manually split up data amongst GPUs / nodes - High-level GPU GPU Xe LinkMulti-GPU Systems - NUMA regions: - 4+ GPUs - 2+ CPUs CPU NIC GPU GPU GPU GPU Xe LinkMulti-GPU Systems - NUMA regions: - 4+ GPUs - 2+ CPUs - Systems becoming more hierarchical: GPU Tile 1 Tile 0 Xe LinkProject Goals - Offer high-level, standard C++ distributed data structures - Support distributed algorithms - Achieve high performance for both multi-GPU, NUMA, and multi-node

file-system caching as the previous level and adds support for distributed cachingCaching Level 4 - Bazel Supports file-system and distributed caching as with the previous level, but based on the digest cache and/or run targets on a shared distributed systemDistributed/remote builds The ability of a build system to cache and/or run targets on a shared distributed system * also known as the thing that that pays my salary :)Distributed builds Level 1 - Make, Ninja, Meson No distributed caching or execution out of the box, everything runs locallyDistributed builds Level 2 - Gradle Has support for

candidate at Berkeley - Advised by Kathy Yelick and Aydın Buluç - Work on large-scale parallel systems - Use a lot of LBL, ORNL supercomputersThis Talk Background: how do we write a program for a supercomputer supercomputer? Introduce PGAS Model, RDMA Building Remote Pointer Types Building Distributed Data Structures Extending to GPUsThis Talk Background: how do we write a program for a supercomputer? Introduce Introduce PGAS Model, RDMA Building Remote Pointer Types Building Distributed Data Structures Extending to GPUsThis Talk Background: how do we write a program for a supercomputer? Introduce PGAS Model

best practices in embedded systems, with a focus on operating systemsToday’s spotlight: Exploring best practices in embedded systems, with a focus on operating systems Today’s take away: Practical Practical tips for building better software, applicable not only to embedded systems but also to software in generalEvery rule presented here comes with an exception Software isn't black and whiteThe code are for illustration⊡ Operating Systems ⊡ Threads ⊡ Layer Separation ⊡ Network Problems ⊡ External Interfaces ⊡ Simulators ⊡ Logs ⊡ Monitoring⊡ Operating Systems ⊡ Threads ⊡ Layer Separation

Ultrafast Trading Systems in C++ CppCon 2024 Thursday, 19 September 2024 David Gross Introduction 2 • About me - Leading the Options Automated Trading Systems team at Optiver market maker company - Worked on low-latency systems for 15 years in Trading and DefenseIntroduction 3 • About me - Leading the Options Automated Trading Systems team at Optiver, a global market maker company company - Worked on low-latency systems for 15 years in Trading and Defense • Today’s talk - Engineering low-latency trading systems - Profiling techniques to find bottlenecks - Some principles along

erasurekey challenges we’ve faced building distributed systems with good performance and correctnesskey challenges we’ve faced building distributed systems with good performance and correctnesschallenges correctnesschallenges building systemschallenges building systems (1) you have to wait (2) you have statechallenges building systems (1) you have to wait (2) you have statemotivating example std::string text = " GrammarCheck(text); // Can be a Future or T. }); }challenges building systems (1) you have to wait ✅ (2) you have statechallenges building systems (1) you have to wait ✅ (2) you have stateexecuting code with

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.4 All platforms, all build systems and compilers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.5 Stable . . . . . cache: concurrency, Continuous Integration, isolation . . . . . . . . . . . . . . . . . . . 160 12 Systems and cross building 163 12.1 Cross building . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 14.2 Build systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.4 All platforms, all build systems and compilers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.5 Stable . . . . . cache: concurrency, Continuous Integration, isolation . . . . . . . . . . . . . . . . . . . 160 12 Systems and cross building 163 12.1 Cross building . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 14.2 Build systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205