Optimizing Build Times with the Gradle Build Cache
Learn how to eliminate redundant build times in Gradle by implementing local and remote build caching to reuse task outputs across environments.
Loading…
ReadMeFeed / Community knowledge
#build-performance
Real questions. Useful conversations. Find the people who know your stack.
gradleCut Build Times with Gradle’s Build Cache and Incremental Compilation
Discover how Gradle’s build cache and incremental compilation can slash rebuild times in multi‑module projects. Learn the setup, a concrete example, and trade‑offs you need to watch out for.
Scaling Link-Time Optimization with LLVM ThinLTO
ThinLTO balances compile‑time speed and runtime performance by generating compact summaries during compilation and performing global optimizations in parallel, reducing link time by up to 70% while still delivering most of the benefits of full LTO.
llvmUsing Bazel Remote Caching to Speed Up CI Builds
Learn how to enable Bazel remote caching, avoid common pitfalls, and verify that your CI builds are actually reusing cached outputs.
bazelWhen webpack 5's Filesystem Cache Is Worth It: An Architecture Note
An architecture note on webpack 5's persistent filesystem cache: when rebuild frequency justifies it, the smallest safe configuration, why the cache directory is untrusted disposable state, and how to verify invalidation actually works.
webpackSVGO Multipass: When More Passes Mean Better Compression
SVGO’s multipass feature applies its plugin set repeatedly until no further size reduction occurs. This blog explains the mechanism, shows a concrete configuration example, discusses performance trade‑offs, and gives actionable steps for developers to use multipass safely.
svgoSpeeding Monorepo Builds with Bazel Remote Cache and Remote Execution
Bazel’s remote cache can turn slow monorepo builds into fast, distributed pipelines. Learn how to configure caching, add remote execution, and monitor hit ratios to cut wall‑clock time.
How can I measure and diagnose performance bottlenecks in CMake's configure and generate steps?
When working with large CMake projects, the configuration and generation phases can become slow. What systematic approaches (e.g., using CMake's --trace, --trace-expand, time commands, or external profiling tools) can be employed to measure where time is spent, and how can the results be interpreted to identify and mitigate bottlenecks?
Balancing CSS minification and source map precision in PostCSS
PostCSS utilizes an Abstract Syntax Tree (AST) to transform CSS through a sequential pipeline of plugins. In low-traffic or small-scale workloads, reducing build-time resource consumption often involves optimizing the plugin chain to minimize memory overhead during AST traversal. A conflict arises when implementing aggressive minification plugins alongside s
postcss