From b6f4798319a91913774b09d758b273351af1d250 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Motiejus=20Jak=C5=A1tys?= Date: Tue, 20 Dec 2022 12:54:45 +0200 Subject: [PATCH] add more prose to README --- README.md | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 585de51..d179a82 100644 --- a/README.md +++ b/README.md @@ -105,10 +105,25 @@ Explanation: recommended with both bazel-zig-cc and a nontrivial sysroot. As a result, this is the most important benchmark to look at. + +Extracting the fastest meaningful benchmarks in all categories: + + 'bazel build --experimental_reuse_sandbox_directories //...' ran + 2.77 ± 0.08 times faster than 'bazel build --extra_toolchains=@llvm_toolchain_with_sysroot//:cc-toolchain-x86_64-linux --experimental_reuse_sandbox_directories //...' + 2.85 ± 0.07 times faster than 'bazel build --platforms=@zig_sdk//libc_aware/platform:linux_amd64_gnu.2.28 --experimental_reuse_sandbox_directories //...' + +This demonstrates that **adding a hermetic toolchain to a project caused 177% +slowdown on this project**. Note that we are not counting `llvm_toolchain//...` +as a real toolchain -- one needs a sysroot to compile anything meaningful +anyway (which zig bundles with the compiler). + +Once we have determined that a hermetic C++ toolchain is required, bazel-zig-cc +is about 2.8% slower than its contender plain llvm14. + Flame graphs and discussion --------------------------- -Flame graphs in results/. Only of historical interest, because the original +Flame graphs in results/. Only of historical interest, because the biggest performance issues have been resolved with a combination of zig and bazel-zig-cc changes.