aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorAlexandre Rames <alexandre.rames@linaro.org>2015-11-26 11:46:23 +0000
committerLinaro Android Code Review <android-review@review.linaro.org>2015-11-26 11:46:23 +0000
commit28166daea4b9478536af60b3710d7d545c5e66d2 (patch)
tree5ef9e6a9fb165e407521fe1bd5d12a57c956ce1f /README.md
parente816f850d3f602191c3c5e7eb458be6c1650fac7 (diff)
parentf2c567f5ea0ac769c439318a89ae68fa7d6de92c (diff)
downloadart-testing-28166daea4b9478536af60b3710d7d545c5e66d2.tar.gz
Merge "Extend the ART testing framework to collect extra statistics."
Diffstat (limited to 'README.md')
-rw-r--r--README.md14
1 files changed, 10 insertions, 4 deletions
diff --git a/README.md b/README.md
index 9df4bfd..4b36eda 100644
--- a/README.md
+++ b/README.md
@@ -3,16 +3,22 @@
## How to Run
-You can run the benchmarks with the `run.py` script. The Android environment
-must be set up, and the board connected via adb. See `run.py --help` for
-details.
+You can run the benchmarks with the `run.py` script, and obtain compilation
+statistics from a target adb device using `compile_stats.py`. Running on a
+device requires that the Android environment be set up, and the device be
+connected via adb. See either `run.py --help` or `compile_stats.py --help`
+for details.
For example you can run on a target adb device:
- ./run.py --iterations 5 --mode 64 --target
+ ./run.py --iterations 5 --mode 64 --target
Or on the host, with no adb device:
./run.py --iterations 5
+Running 5 iterations of the compilation process with the benchmarks and all
+APK files in ~/apk:
+ ./compile_stats.py -i5 build/bench.apk ~/apk
+
## How to Write a Benchmark
Each set of related benchmarks is implemented as a Java class and kept in the