| commit | 5d98324022a156542b768849d4dedcde49eb67d0 | [log] [tgz] |
|---|---|---|
| author | adonovan <adonovan@google.com> | Wed May 13 15:02:49 2020 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed May 13 15:04:05 2020 -0700 |
| tree | 6840afb5da54ee0a7db46ed121158557905a9336 | |
| parent | c7dc024dbe9b84610646c3bcfa97f68ef63bb659 [diff] |
bazel syntax: stop creating wall-time profiler spans for each function call We have a CPU profiler now, which is more accurate in the presence of parallelism, as every runnable but not running thread accumulates wall time even as it does nothing. (Also, I saw no sign of these spans in when running blaze query --experimental_generate_json_trace_profile deps(X) where X is a Substantial Program.) The higher-level unit of BUILD/.bzl file execution is a more appropriate span. PiperOrigin-RevId: 311411836
{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:
See CONTRIBUTING.md
