Bazel Remote Execution API vs. Goma + Q&A

on YouTube ↗28m

" summary

Compares GMA (Google’s compiler proxy) and Bazel Remote Execution via wreck by actually building Chromium subsets, using both Clang and GCC, and running a private back end with memcached and Bazel remote action cache. Finds GMA hot-cache: ~1 minute rebuild versus RBE (wreck) hot-cache: ~4 minute rebuild, notes wreck does single-run RPCs per compile, heavy client CPU for Merkle trees and digests, DNS overhead, and that a prototype RBE execution service builds useful subsets and populates cache.

AI-written summary · about

" chapters (10)

1. 0:00Introduction
2. 3:13Chromium build pain points
3. 6:20Goma client overview
4. 10:10Goma backend design
5. 13:25Remote Execution vs Goma
6. 15:54Remote Execution prototype
7. 17:22Performance results
8. 21:17Key learnings
9. 23:46Summary
10. 24:08Q&A

" related talks

• 10mHow Bazel Handles GlobsNathan Harmata · BazelCon 2024
• 29mGraalVM in a NutshellSachin Pikle · Great International Developer Summit 2024
• 15mNot So Fast: Understanding and Mitigating Negative Impacts of Compiler Optimizations on Code Reuse GGirish Mururu, Santosh Pande, Michael D. Brown, Matthew Pruett, Robert Bigelow · OOPSLA 2021
• 31mSimplifying and Optimizing Life on the Edge with GraalScott Lynn · swampUP 2017
• 23mAdopting GraalVMPetr Zapletal · Scale By The Bay 2018
• 48mOne VM To Rule Them AllThomas Wuerthinger · JavaDay Kyiv 2015
• 33mNew Opportunities for Developers with GraalVMAlina Yurenko · JAX London 2019
• 37mGraalVM for Polyglots: Harder, Better, Faster, Stronger?Diogo Souza · The Conf 2019