reserved. Remote Execution Caching Compiler (RECC) CppCon 2024 September 19, 2024 Shivam Bairoliya Software Engineer© 2024 Bloomberg Finance L.P. All rights reserved. What is RECC? ● Remote Execution compiler commands and optionally forwards them to a remote build execution service ○ Encompasses the capabilities of both ccache and distcc ○ Supports remote linking and caching ● Designed to share caches Solaris CC) ○ Supports multiple operating systems (Linux, macOS, Solaris) ● Compatible with any remote execution API server supported by Bazel ○ Single Host Server/Proxy: BuildBox-CASD ○ Distributed

read/write to remote memory Node 0 Node 1 Write 12 -> 0x8f Communication Mechanisms- Message Passing - processes issue matching send and receive calls - RDMA - directly read/write to remote memory Node Node 0 Node 1 Write 12 -> 0x8f auto remote_ptr = ...; // Calculate data auto values = algorithm(1.0f, 3, data); // Send data to proc. 1 memcpy(remote_ptr, values.data(), values.size()*sizeof(float)); directly read/write to remote memory Node 0 Node 1 Write 12 -> 0x8f auto remote_ptr = ...; // Calculate data auto values = algorithm(1.0f, 3, data); // Send data to proc. 1 memcpy(remote_ptr, values.data()

create and test packages offline. You can also work offline so long as no new packages are needed from remote servers. • The Conan server: this is a TCP server that can be easily run as your own server on-premises packages generated from a package recipe are managed and stored coherently. When they are uploaded to a remote, they stay connected. Also, different clients building binaries from the same package recipe (like our application relies on the Poco libraries. Let’s look for it in the Conan Center remote: $ conan search Poco* --remote=conan-center Existing package recipes: Poco/1.7.8p3@pocoproject/stable Poco/1.7

create and test packages offline. You can also work offline so long as no new packages are needed from remote servers. • The Conan server: this is a TCP server that can be easily run as your own server on-premises packages generated from a package recipe are managed and stored coherently. When they are uploaded to a remote, they stay connected. Also, different clients building binaries from the same package recipe (like our application relies on the Poco libraries. Let’s look for it in the Conan Center remote: $ conan search Poco* --remote=conan-center Existing package recipes: (continues on next page) 11 conan Documentation

create and test packages offline. You can also work offline so long as no new packages are needed from remote servers. • The Conan server: this is a TCP server that can be easily run as your own server on-premises packages generated from a package recipe are managed and stored coherently. When they are uploaded to a remote, they stay connected. Also, different clients building binaries from the same package recipe (like our application relies on the Poco libraries. Let’s look for it in the Conan Center remote: $ conan search Poco* --remote=conan-center Existing package recipes: (continues on next page) 11 conan Documentation

create and test packages offline. You can also work offline so long as no new packages are needed from remote servers. • The Conan server: this is a TCP server that can be easily run as your own server on-premises packages generated from a package recipe are managed and stored coherently. When they are uploaded to a remote, they stay connected. Also, different clients building binaries from the same package recipe (like our application relies on the Poco libraries. Let’s look for it in the Conan Center remote: $ conan search Poco* --remote=conan-center Existing package recipes: (continues on next page) 11 conan Documentation

create and test packages offline. You can also work offline so long as no new packages are needed from remote servers. • The Conan server: this is a TCP server that can be easily run as your own server on-premises packages generated from a package recipe are managed and stored coherently. When they are uploaded to a remote, they stay connected. Also, different clients building binaries from the same package recipe (like our application relies on the Poco libraries. Let’s look for it in the Conan Center remote: $ conan search Poco --remote=conan-center Existing package recipes: (continues on next page) 11 Conan Documentation

create and test packages offline. You can also work offline so long as no new packages are needed from remote servers. • The Conan server: this is a TCP server that can be easily run as your own server on-premises packages generated from a package recipe are managed and stored coherently. When they are uploaded to a remote, they stay connected. Also, different clients building binaries from the same package recipe (like our application relies on the Poco libraries. Let’s look for it in the Conan Center remote: $ conan search Poco --remote=conan-center Existing package recipes: (continues on next page) 11 Conan Documentation

create and test packages offline. You can also work offline so long as no new packages are needed from remote servers. • The Conan server: this is a TCP server that can be easily run as your own server on-premises packages generated from a package recipe are managed and stored coherently. When they are uploaded to a remote, they stay connected. Also, different clients building binaries from the same package recipe (like our application relies on the Poco libraries. Let’s look for it in the Conan Center remote: $ conan search Poco* --remote=conan-center Existing package recipes: Poco/1.7.8p3@pocoproject/stable Poco/1.7

create and test packages offline. You can also work offline so long as no new packages are needed from remote servers. • The Conan server: this is a TCP server that can be easily run as your own server on-premises packages generated from a package recipe are managed and stored coherently. When they are uploaded to a remote, they stay connected. Also, different clients building binaries from the same package recipe (like our application relies on the Poco libraries. Let’s look for it in the Conan Center remote: $ conan search Poco* --remote=conan-center Existing package recipes: Poco/1.7.8p3@pocoproject/stable Poco/1.7