From aa22c0cb0c25d6462547bc1557c08a18b176147b Mon Sep 17 00:00:00 2001 From: Christopher Ferris Date: Wed, 14 Aug 2019 15:17:26 -0700 Subject: [PATCH] Update location of trace files. Test: NA Change-Id: I27f98b84b7701b8747d22dbdfbfa074083c36bc1 --- docs/native_allocator.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/native_allocator.md b/docs/native_allocator.md index 2d06e2f3e..82a98fe48 100644 --- a/docs/native_allocator.md +++ b/docs/native_allocator.md @@ -266,16 +266,16 @@ the option [record\_allocs](https://android.googlesource.com/platform/bionic/+/m To run these benchmarks, first copy the trace files to the target and unzip them using these commands: - adb shell push system/extras/dumps /data/local/tmp - adb shell 'cd /data/local/tmp/dumps && for name in *.zip; do unzip $name; done' + adb shell push system/extras/traces /data/local/tmp + adb shell 'cd /data/local/tmp/traces && for name in *.zip; do unzip $name; done' Since all of the traces come from applications, the `memory_replay` program will always call `mallopt(M_DECAY_TIME, 1)' before running the trace. Run the benchmark thusly: - adb shell memory_replay64 /data/local/tmp/dumps/XXX.txt - adb shell memory_replay32 /data/local/tmp/dumps/XXX.txt + adb shell memory_replay64 /data/local/tmp/traces/XXX.txt + adb shell memory_replay32 /data/local/tmp/traces/XXX.txt Where XXX.txt is the name of a trace file.