commit dad21edeeaca1a5f539730dbede1a1e7f6b0ffeb
author laurentlb <laurentlb@google.com> Wed May 13 16:00:41 2020 -0700
committer Copybara-Service <copybara-worker@google.com> Wed May 13 16:01:41 2020 -0700
tree 7d3419584d190c1eac2b8652f736e858b9d8026c
parent 1057827dc7725a425f4b14147d594b8a97073e16

Fix formatting

An internal tag was not closed properly.

RELNOTES: None.
PiperOrigin-RevId: 311422220

site/docs/user-manual.html

diff --git a/site/docs/user-manual.html b/site/docs/user-manual.html
index 0910a25..c2072a5 100644
--- a/site/docs/user-manual.html
+++ b/site/docs/user-manual.html
@@ -2725,6 +2725,23 @@
 <p>For example:</p>
 <pre><code>
   OUTPUT_BASE=/var/tmp/google/_bazel_johndoe/custom_output_base
+  % bazel --output_base $OUTPUT_BASE build //foo  &amp;  bazel --output_base $OUTPUT_BASE build //bar
+</code></pre>
+<p>
+  In this command, the two Bazel commands run concurrently (because of
+  the shell <code>&amp;</code> operator), each using a different Bazel
+  server instance (because of the different output bases).
+  In contrast, if the default output base was used in both commands,
+  then both requests would be sent to the same server, which would
+  handle them sequentially: building <code>//foo</code> first, followed
+  by an incremental build of <code>//bar</code>.
+</p>
+<p>
+  We recommend you do not use NFS locations for the output base, as
+  the higher access latency of NFS will cause noticeably slower
+  builds.
+</p>
+
 <h4 id='flag--output_user_root'><code class='flag'>--output_user_root=<var>dir</var></code></h4>
 <p>
   By default, the <code>output_base</code> value is chosen to as to