diff options
| author |  brandjon <brandjon@google.com> | 2018-01-29 07:54:17 -0800 |
|---|---|---|
| committer |  Copybara-Service <copybara-piper@google.com> | 2018-01-29 07:56:20 -0800 |
| commit | a79f42fbd35a614effaec2cfc3b773694ca3d844 (patch) | |
| tree | 3919eebbaac9f27d72abc261d1b7ec94392e1ba6 /site/docs/skylark/performance.md | |
| parent | 79ebb32e77f134e2f6496dd532bf9574d4198676 (diff) | |
Doc formatting fix, take two
Follow-up to https://github.com/bazelbuild/bazel/commit/210cdeb8a7836c5fd586a29d73c8013f325d3883
RELNOTES: None
PiperOrigin-RevId: 183665009
Diffstat (limited to 'site/docs/skylark/performance.md')
| -rw-r--r-- | site/docs/skylark/performance.md | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/site/docs/skylark/performance.md b/site/docs/skylark/performance.md index ac36888db8..9b77a01433 100644 --- a/site/docs/skylark/performance.md +++ b/site/docs/skylark/performance.md @@ -207,7 +207,6 @@ You must pass these two startup flags to *every* Bazel invocation: ``` **NOTE**: The bazel repository comes with an allocation instrumenter. Make sure to adjust '$(BAZEL)' for your repository location. ---> These start the server in memory tracking mode. If you forget these for even one Bazel invocation the server will restart and you will have to start over. @@ -260,7 +259,6 @@ Next, we use the `pprof` tool to investigate the heap. A good starting point is getting a flame graph by using `pprof -flame $HOME/prof.gz`. You can get `pprof` from https://github.com/google/pprof. ---> In this case we get a text dump of the hottest call sites annotated with lines: |