Move profiling information from the Overview to the Optimizing page.
RELNOTES: None.
PiperOrigin-RevId: 179037412
diff --git a/site/docs/skylark/concepts.md b/site/docs/skylark/concepts.md
index 80b8981..b7cda34 100644
--- a/site/docs/skylark/concepts.md
+++ b/site/docs/skylark/concepts.md
@@ -92,15 +92,3 @@
be loaded, which rules must be analyzed, and which actions must be executed. For
example, if a rule generates actions that we don't need for the current build,
they will not be executed.
-
-
-## Profiling the code
-
-To profile your code and analyze the performance, use the `--profile` flag:
-
-```
-$ bazel build --nobuild --profile=/tmp/prof //path/to:target
-$ bazel analyze-profile /tmp/prof --html --html_details
-```
-
-Then, open the generated HTML file (`/tmp/prof.html` in the example).
diff --git a/site/docs/skylark/performance.md b/site/docs/skylark/performance.md
index 4538bfd..ac36888 100644
--- a/site/docs/skylark/performance.md
+++ b/site/docs/skylark/performance.md
@@ -179,6 +179,17 @@
)
```
+## Performance profiling
+
+To profile your code and analyze the performance, use the `--profile` flag:
+
+```
+$ bazel build --nobuild --profile=/tmp/prof //path/to:target
+$ bazel analyze-profile /tmp/prof --html --html_details
+```
+
+Then, open the generated HTML file (`/tmp/prof.html` in the example).
+
## Memory Profiling
Bazel comes with a built-in memory profiler that can help you check your rule's
