Merge "Mention SOONG_UI_NINJA_ARGS in perf.md" am: 1b0939ab87
am: fe90a301b2
am: 0ea0413cff
am: baa4bac857
am: bce890f606
Original change: https://android-review.googlesource.com/c/platform/build/soong/+/2200762 Change-Id: Ied572920be39332a9d11acf3f7bf3a6e3c2769e5 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
This commit is contained in:
commit
3ff81f34e7
1 changed files with 13 additions and 1 deletions
14
docs/perf.md
14
docs/perf.md
|
@ -221,6 +221,18 @@ You'll likely need to cross-reference this data against the build graph in the
|
|||
various .ninja files. The files are (mostly) human-readable, but a (slow) web
|
||||
interface can be used by running `NINJA_ARGS="-t browse <target>" m`.
|
||||
|
||||
There is also `SOONG_UI_NINJA_ARGS`, which passes ninja arguments to soong ui's
|
||||
ninja invocations, e.g. to emit $OUT_DIR/soong/build.ninja, $OUT_DIR/soong/module-graph.json, etc.
|
||||
|
||||
```bash
|
||||
$ m nothing
|
||||
$ touch Android.bp
|
||||
$ SOONG_UI_NINJA_ARGS="-d explain" m nothing
|
||||
...
|
||||
ninja explain: restat of output out/soong/build.ninja older than most recent input Android.bp
|
||||
...
|
||||
```
|
||||
|
||||
#### Builds take a long time
|
||||
|
||||
If the long part in the trace view of a build is a relatively solid block, then
|
||||
|
@ -228,7 +240,7 @@ the performance is probably more related to how much time the actual build
|
|||
commands are taking than having extra dependencies, or slowdowns in
|
||||
soong/kati/ninja themselves.
|
||||
|
||||
Beyond looking at visible outliers in the trace view, we don't have any tooling
|
||||
Beyond looking at visible outliers in the trace view, we don't have any tooli
|
||||
to help in this area yet. It's possible to aggregate some of the raw data
|
||||
together, but since our builds are heavily parallelized, it's particularly easy
|
||||
for build commands to impact unrelated build commands. This is an area we'd
|
||||
|
|
Loading…
Reference in a new issue