conclusions 1. Support building from source 2. Build a verified binary cache 3. Version using baselines 4. Build open-source with a package manager 5. Cache build assets internally 6. Monitor, prevent version ? Consuming projectProblem 3: Version conflicts – The Diamond problem Solution 3: Manage baselines, not individual libraries boost@v1 openssl@v1 gtest@v1 … Catalog baseline: b60f003ccf5fe8613 CppCon 2021 talk from BloombergProblem 3: Version conflicts – The Diamond problem Solution 3: Manage baselines, not individual libraries Test version updates using the “cones of destruction” method Library

external systems. As with CM on traditional programs, there needs to be rigor on managing changes to baselines, designs, engineering, and program documentation. Some additional CM methods for Agile include: place to ensure rigorous configuration management of requirements, code, technical designs, and baselines?  What is the continuous improvement strategy? See also: Agile architecture articles 10 meets the design-to or build-to specifications defined in the functional, allocated, and product baselines. In an Agile environment verification is an integral element of each sprint. At the end of each

real-world application • Conclusion 74Hardware Platform & Baselines • Eight CPU threads (3.2 GHz) • One NVIDIA 3080 ti GPU • Baselines - Microbenchmarks • Taskflow • 𝐓𝐚𝐬𝐤𝐟𝐥𝐨𝐰𝐜𝐨𝐫𝐨 1

sampling model running in 30us on single server CPU core - Beat hand-written, highly optimized baselines (https://github.com/mozilla/LPCNet) by ~40% - Bonus: Real-time on mobile CPUs for free 6 TVM

global_variables) • Other system tables +-----------------------------------------------------+ | capture_plan_baselines_blacklist | | column_stats_usage | | gc_delete_range | | gc_delete_range_done | | global_variables matches one of the bound SQL statements in the system table and the system variable tidb_use_plan �→ _baselines is set to on (the default value is on), TiDB then uses the corresponding optimizer hint for this reproduce an execution plan. Enable capturing To enable baseline capturing, set tidb_capture_plan_baselines to on. The default value is off. Note: Because the automatic binding creation function relies

global_variables) • Other system tables +-----------------------------------------------------+ | capture_plan_baselines_blacklist | | column_stats_usage | | gc_delete_range | | gc_delete_range_done | | global_variables matches one of the bound SQL statements in the system table and the system variable tidb_use_plan �→ _baselines is set to on (the default value is on), TiDB then uses the corresponding optimizer hint for this reproduce an execution plan. Enable capturing To enable baseline capturing, set tidb_capture_plan_baselines to on. The default value is off. Note: Because the automatic binding creation function relies

global_variables) • Other system tables +-----------------------------------------------------+ | capture_plan_baselines_blacklist | | column_stats_usage | | gc_delete_range | | gc_delete_range_done | | global_variables matches one of the bound SQL statements in the system table and the system variable tidb_use_plan �→ _baselines is set to on (the default value is on), TiDB then uses the corresponding optimizer hint for this reproduce an execution plan. Enable capturing To enable baseline capturing, set tidb_capture_plan_baselines to on. The default value is off. Note: Because the automatic binding creation function relies

global_variables) • Other system tables +-----------------------------------------------------+ | capture_plan_baselines_blacklist | | column_stats_usage | | gc_delete_range | | gc_delete_range_done | | global_variables matches one of the bound SQL statements in the system table and the system variable tidb_use_plan �→ _baselines is set to on (the default value is on), TiDB then uses the corresponding optimizer hint for this reproduce an execution plan. Enable capturing To enable baseline capturing, set tidb_capture_plan_baselines to on. The default value is off. Note: Because the automatic binding creation function relies

global_variables) • Other system tables +-----------------------------------------------------+ | capture_plan_baselines_blacklist | | column_stats_usage | | gc_delete_range | | gc_delete_range_done | | global_variables matches one of the bound SQL statements in the system table and the system variable tidb_use_plan �→ _baselines is set to on (the default value is on), TiDB then uses the corresponding optimizer hint for this reproduce an execution plan. Enable capturing To enable baseline capturing, set tidb_capture_plan_baselines to on. The default value is off. Note: Because the automatic binding creation function relies

global_variables) • 其他系统表 +-----------------------------------------------------+ | capture_plan_baselines_blacklist | | column_stats_usage | | gc_delete_range | | gc_delete_range_done | | global_variables SQL 进行 “标准化” 处理，然后存储到系统表中。在处理 SQL 查询时，只要 “标准化” 后的 SQL 和系统表中某个被绑 定的 SQL 语句一致，并且系统变量tidb_use_plan_baselines 的值为 on（其默认值为 on），即可使用相应的优 化器 Hint。如果存在多个可匹配的执行计划，优化器会从中选择代价最小的一个进行绑定。 1447 标准化：把 SQL 中的常量变成变量 Baseline 中。这些计划包含优化器重新生成执行计划所需的所有信息（例如，SQL 计划标 识符、提示集、绑定值、优化器环境）。 使用方式 通过将 tidb_capture_plan_baselines 的值设置为 on（其默认值为 off）可以打开自动捕获绑定功能。 注意： 自动绑定功能依赖于Statement Summary，因此在使用自动绑定之前需打开 Statement Summary