diff options
| author |  ncteisen <ncteisen@gmail.com> | 2017-06-07 11:50:04 -0700 |
|---|---|---|
| committer | ncteisen <ncteisen@gmail.com> | 2017-06-07 11:50:04 -0700 |
| commit | f1e19fdd3118d36316223b6720f08e3aadcc2b4a (patch) | |
| tree | c0259883131dacf45c9578c4755286827e5515ed /tools/profiling | |
| parent | c7586a5d32cd07b0151df020e8982f127514b496 (diff) | |
Fix typos in README
Diffstat (limited to 'tools/profiling')
| -rw-r--r-- | tools/profiling/microbenchmarks/bm_diff/README.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/tools/profiling/microbenchmarks/bm_diff/README.md b/tools/profiling/microbenchmarks/bm_diff/README.md index 3d01ea25ba..caa4770229 100644 --- a/tools/profiling/microbenchmarks/bm_diff/README.md +++ b/tools/profiling/microbenchmarks/bm_diff/README.md @@ -6,7 +6,7 @@ different performance tweaks. The tools allow you to save performance data from a baseline commit, then quickly compare data from your working branch to that baseline data to see if you have made any performance wins. -The tools operates with three concrete steps, which can be invoked separately, +The tools operate with three concrete steps, which can be invoked separately, or all together via the driver script, bm_main.py. This readme will describe the typical workflow for these scripts, then it will include sections on the details of every script for advanced usage. @@ -39,7 +39,7 @@ the output to the saved runs from master. If you have a deeper knowledge of these scripts, you can use them to do more fine tuned benchmark comparisons. For example, you could build, run, and save the benchmark output from two different base branches. Then you could diff both -of these baselines against you working branch to see how the different metrics +of these baselines against your working branch to see how the different metrics change. The rest of this doc goes over the details of what each of the individual modules accomplishes. |