diff options
| author |  tomlu <tomlu@google.com> | 2017-10-30 18:01:48 -0400 |
|---|---|---|
| committer |  John Cater <jcater@google.com> | 2017-10-31 10:37:43 -0400 |
| commit | 5af6138f293985bb13e3ae46eab7ac8e10ab6db1 (patch) | |
| tree | 0f62c363782ee71f32b2d39899c558b417113a9b /site/docs/user-manual.html | |
| parent | 61c48b50fe7d8b1bd491a20d35f851be90bf07d2 (diff) | |
Internal change
PiperOrigin-RevId: 173955012
Diffstat (limited to 'site/docs/user-manual.html')
| -rw-r--r-- | site/docs/user-manual.html | 68 |
1 files changed, 33 insertions, 35 deletions
diff --git a/site/docs/user-manual.html b/site/docs/user-manual.html index d6899803f2..096688f582 100644 --- a/site/docs/user-manual.html +++ b/site/docs/user-manual.html @@ -3246,42 +3246,40 @@ adb -s deadbeef install ... You must enable memory tracking for this to work.</li> </ul> - --> -<h4 id='memory-tracking'>Memory tracking</h4> -<p> - Some <code>dump</code> commands require memory tracking. To turn this on, you have to pass - startup flags to Bazel: -</p> -<ul> - <li><code>--host_jvm_args=-javaagent:$BAZEL/third_party/allocation_instrumenter/java-allocation-instrumenter-3.0.1.jar</code></li> - <li><code>--host_jvm_args=-DBLAZE_MEMORY_TRACKER=1</code></li> -</ul> -<p> - The java-agent is checked into bazel at - third_party/allocation_instrumenter/java-allocation-instrumenter-3.0.1.jar, so make - sure you adjust <code>$BAZEL</code> for where you keep your bazel repository. - - Do not forget to keep passing these options to Bazel for every command or the server will - restart. -</p> -<p>Example:</p> -<pre> - % bazel --host_jvm_args=-javaagent:$BAZEL/third_party/allocation_instrumenter/java-allocation-instrumenter-3.0.1.jar \ - --host_jvm_args=-DRULE_MEMORY_TRACKER=1 \ - build --nobuild <targets> - - # Dump rules - % bazel --host_jvm_args=-javaagent:$BAZEL/third_party/allocation_instrumenter/java-allocation-instrumenter-3.0.1.jar \ - --host_jvm_args=-DRULE_MEMORY_TRACKER=1 \ - dump --rules - - # Dump Skylark heap and analyze it with pprof - % bazel --host_jvm_args=-javaagent:$BAZEL/third_party/allocation_instrumenter/java-allocation-instrumenter-3.0.1.jar \ - --host_jvm_args=-DRULE_MEMORY_TRACKER=1 \ - dump --skylark_memory=$HOME/prof.gz - % pprof -flame $HOME/prof.gz -</pre> + <h4 id='memory-tracking'>Memory tracking</h4> + <p> + Some <code>dump</code> commands require memory tracking. To turn this on, you have to pass + startup flags to Bazel: + </p> + <ul> + <li><code>--host_jvm_args=-javaagent:$BAZEL/third_party/allocation_instrumenter/java-allocation-instrumenter-3.0.1.jar</code></li> + <li><code>--host_jvm_args=-DBLAZE_MEMORY_TRACKER=1</code></li> + </ul> + <p> + The java-agent is checked into bazel at + third_party/allocation_instrumenter/java-allocation-instrumenter-3.0.1.jar, so make + sure you adjust <code>$BAZEL</code> for where you keep your bazel repository. + Do not forget to keep passing these options to Bazel for every command or the server will + restart. + </p> + <p>Example:</p> + <pre> + % bazel --host_jvm_args=-javaagent:$BAZEL/third_party/allocation_instrumenter/java-allocation-instrumenter-3.0.1.jar \ + --host_jvm_args=-DRULE_MEMORY_TRACKER=1 \ + build --nobuild <targets> + + # Dump rules + % bazel --host_jvm_args=-javaagent:$BAZEL/third_party/allocation_instrumenter/java-allocation-instrumenter-3.0.1.jar \ + --host_jvm_args=-DRULE_MEMORY_TRACKER=1 \ + dump --rules + + # Dump Skylark heap and analyze it with pprof + % bazel --host_jvm_args=-javaagent:$BAZEL/third_party/allocation_instrumenter/java-allocation-instrumenter-3.0.1.jar \ + --host_jvm_args=-DRULE_MEMORY_TRACKER=1 \ + dump --skylark_memory=$HOME/prof.gz + % pprof -flame $HOME/prof.gz + </pre> <h3 id='analyze-profile'>The <code>analyze-profile</code> command</h3> <p> |