Remove obsolete information on how to create the profile.
Part of https://github.com/bazelbuild/bazel/issues/11384.
RELNOTES: None
PiperOrigin-RevId: 326005171
diff --git a/site/docs/android-build-performance.md b/site/docs/android-build-performance.md
index c9ea15f..f5887b4 100644
--- a/site/docs/android-build-performance.md
+++ b/site/docs/android-build-performance.md
@@ -18,19 +18,11 @@
**Profiling performance**
-This set of flags generates a JSON trace profile, `profile.json.gz`, that
-can be viewed using the Chrome Tracing Profiler (`chrome://tracing`). See
-the [JSON Profile documentation](skylark/performance.html#json-profile) for
+Bazel writes a JSON trace profile by default to a file called
+`command.profile.gz` in Bazel's output base.
+See the [JSON Profile documentation](skylark/performance.html#json-profile) for
how to read and interact with the profile.
-```
-build:profile --experimental_generate_json_trace_profile
-build:profile --profile profile.json.gz
-build:profile --experimental_json_trace_compression
-```
-
-These flags can be used by specifying `--config=profile` on the command line.
-
**Persistent workers for Android build actions**.
A subset of Android build actions has support for
