| commit | d658908d5e581d3ca312a6d8b78d8c6fbe6d7ed3 | [log] [tgz] |
|---|---|---|
| author | Sara Adams <sara@engflow.com> | Wed Jan 25 10:55:48 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Jan 25 10:57:11 2023 -0800 |
| tree | ac29d06ffeba6e4c160d9e320d27b96ea7fadc37 | |
| parent | d5095dbfd320654298aaa1b412a7581b53792d3f [diff] |
Documentation: Add contents of "Build performance metrics" blog post This change includes the contents of the blog post on "Build performance metrics" published at https://blog.bazel.build/2022/11/15/build-performance-metrics.html The content split up and added to different pages: * new page: Extracting build performance metrics This page includes most of the content of the first two sections of the blog post, some content is moved to the "Json Trace Profile" page (see below). * new page: Breaking down build performance This page includes the content of the third (and final) section of the blog post. * new page: JSON Trace Profile This page includes the content of the "Performance profiling" section currently live at https://bazel.build/rules/performance#performance-profiling with some minor updates (new image, new row names), as well as some content from the second section of the blog post (`jq` usage example). * update page: Optimizing memory This page is moved to the newly introduces configure subsection "Build performance" (previously part of "Configuring your build"). In addition, a reference to the "Memory profiling" section of https://bazel.build/rules/performance#memory-profiling is added. * update page: Optimizing Performance (for custom rules) The contents of the "Performance profiling" is moved to the new page "JSON Trace Profile", and points to the new page. The content is not specific to custom rules, but also valuable for optimizing builds in general, so this change attempts to place the content in a more discoverable place and in context of other useful information. Caveat: I could not run the code locally to check whether it renders correctly, whether all links work, etc. Future considerations: In a follow-up change, I would like to add another new page that shows screenshots of different trace profiles (in `chrome://tracing`) and a paragraph on something noteworthy about the profile / how it can help guide was to potentially improve performance. Closes #17034. PiperOrigin-RevId: 504606869 Change-Id: I60af55b924ddaf2f592fe038028f80cf61140a7e
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
