## Remote Execution Caching Compiler (RECC) Engineering CppCon 2024 September 19, 2024 Shivam Bairoliya Software Engineer TechAtBloomberg.com © 2024 Bloomberg Finance L.P. All rights reserved. ## ## What is RECC? • Remote Execution Caching Compiler (RECC) Open source build tool that wraps compiler commands and optionally forwards them to a remote build execution service Encompasses the capabilities CC) o Supports multiple operating systems (Linux, macOS, Solaris) - Compatible with any remote execution API server supported by Bazel ☐ Single Host Server/Proxy: BuildBox-CASD ☐ Distributed Server:

Options Automated Trading Systems team at Optiver, a global market maker company - Worked on low-latency systems for 15 years in Trading and Defense  Ultra low-latency execution (< 1µs) ## Order book deep dive “The order book is the heart of any trading system

## Designing an ultra low-overhead multithreading runtime for Nim Mamy Ratsimbazafy mamy@numforge.co ## Hello! ## I am Mamy Ratsimbazafy During the day blockchain/Ethereum 2 developer (in Nim) During parallelism ## Hardware-level multithreading ILP - Instruction-level Parallelism 1 CPU, multiple "execution ports" SIMD - Single Instruction Multiple Data a.k.a. Vector instructions (SSE, AVX, Neon) Simultaneous Multithreading Hyperthreading (2x logical siblings core usually, 4x on Xeon Phi) Share execution ports, memory bus, caches, ... ## Data parallelism ## Parallel for loop Same instructions on multiple

68ce28/p41_1.jpg) This is the monstrosity in love, lady, that the will is infinite, and the execution confined; that the desire is boundless, and the act a slave to limit. ## Every question has an

## The Vitess Documentation ## Contents Concepts ..... 18 Cell ..... 18 Execution Plans ..... 18 Keyspace ID ..... 19 Keyspace ..... 19 MoveTables ..... 19 Identifying Candidate Tables . cell. Writes will go cross-cell when necessary, to wherever the master for that shard resides. ## Execution Plans Vitess parses queries at both the VTGate and VTTablet layer in order to evaluate the best to execute a query. This evaluation is known as query planning, and results in a query execution plan. The Execution Plan is dependent on both the query and the associated VSchema. One of the underlying

## The Vitess Documentation ## Contents Concepts ..... 11 Cell ..... 11 Execution Plans ..... 11 Keyspace Graph ..... 11 Partitions ..... 12 Served From ..... 12 Keyspace ID ..... 12 Keyspace cell. Writes will go cross-cell when necessary, to wherever the master for that shard resides. ## Execution Plans Vitess parses queries at both the VTGate and VTTablet layer in order to evaluate the best to execute a query. This evaluation is known as query planning, and results in a query execution plan. The Execution Plan is dependent on both the query and the associated VSchema. One of the underlying

the vanilla attention mechanism (Vaswani et al., 2017), which creates a prohibitive bottleneck for ultra-long contexts and reasoning processes. Concurrently, the emergence of long-horizon scenarios and tasks complex agentic workflows to massive cross-document analysis — has also made efficient support for ultra-long contexts critical for future progress. While recent open-source efforts (Bai et al., 2025a; DeepSeek-AI Qwen, 2025) have advanced general capabilities, this core architectural inefficiency in handling ultra-long sequences remains a key impediment, limiting further gains from test-time scaling and hindering

non-real-time OSs or secure and non-secure OSs based on hardware-assisted virtualization, trusted execution environment (TEE), and heterogeneous architectures. It utilizes the characteristics of each OS to https://gitee.com/openeuler/rust_shyper ## UniProton Embedded SIG UniProton is a hard RTOS that delivers ultra-low latency in microseconds and mixed-criticality deployment. It can be deployed together with general-purpose feature a lightweight kernel, optimized performance, and custom functions that combine to achieve ultra-low latency. ## ▶ Project Introduction Huawei is an experienced vendor specializing in hard real-time

Inline Resources 87 6.2.2. Creating Email Content by Using a Templating Library 89 7. Task Execution and Scheduling 90 7.1. The Spring TaskExecutor Abstraction 90 7.1.1. TaskExecutor Types 90 2.3. TaskScheduler implementations 94 7.3. Annotation Support for Scheduling and Asynchronous Execution 95 7.3.1. Enable Scheduling Annotations 95 7.3.2. The @Scheduled annotation 96 7.3.3. The vulnerabilities due to unsafe Java deserialization: Manipulated input streams can lead to unwanted code execution on the server during the deserialization step. As a consequence, do not expose HTTP invoker endpoints

this talk, our primary discussion will be towards achieving data determinism via: • Deterministic execution $ ^{2} $ will always run computations in the same order. - Deterministic communication $ ^{2} to bridge this gap to enable real-time behavior • Controlling memory usage • Controlling task execution • Memory usage • Allocations during runtime • STL constructs with heap usage • std::string fwrite • Non-deterministic execution • No resource allocation during runtime • All operations are finite and bounded • All potentially blocking calls have timeouts • Execution is deterministic and monitored