summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
author Usta Shrestha <usta@google.com> 2022-09-09 23:38:47 -0400
committer Usta Shrestha <usta@google.com> 2022-09-12 11:25:31 -0400
commit607a995f8d527789b19b47e4b973a8ff1cdb40f0 (patch)
treebfbd0500e5cfdcbc0e19d3d69f73c2cd9f88f5ac
parent1b0939ab871e102bf5ccb6b37b38dafb2822b457 (diff)
typo
Test: N/A Bug: N/A Change-Id: I277c126e4e75c5068f0b6e29cff89e56b4bed840
-rw-r--r--docs/perf.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/perf.md b/docs/perf.md
index d71872c94..694dcf135 100644
--- a/docs/perf.md
+++ b/docs/perf.md
@@ -240,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 tooli
+Beyond looking at visible outliers in the trace view, we don't have any tooling
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