summaryrefslogtreecommitdiff
path: root/docs/native_allocator.md
diff options
context:
space:
mode:
authorandroid-build-team Robot <android-build-team-robot@google.com>2019-10-21 06:14:03 +0000
committerandroid-build-team Robot <android-build-team-robot@google.com>2019-10-21 06:14:03 +0000
commit6e4056ca9599bc29a99f6aed2ad1f79f263c28ac (patch)
tree093daa9a0b65a13cacd118dd7b7ff30d37abcdd7 /docs/native_allocator.md
parent586aead5271e37734fe7e56f042a14e459711350 (diff)
parent51146452ac287412715d45e2ab59e826e45b0328 (diff)
Snap for 5954522 from 51146452ac287412715d45e2ab59e826e45b0328 to rvc-release
Change-Id: I448210dbd293262eb2ab0efa7dc2c37171bb5f44
Diffstat (limited to 'docs/native_allocator.md')
-rw-r--r--docs/native_allocator.md13
1 files changed, 7 insertions, 6 deletions
diff --git a/docs/native_allocator.md b/docs/native_allocator.md
index 82a98fe48..76954700f 100644
--- a/docs/native_allocator.md
+++ b/docs/native_allocator.md
@@ -263,21 +263,22 @@ so it is not possible to create a completely accurate replay.
To generate these traces, see the [Malloc Debug documentation](https://android.googlesource.com/platform/bionic/+/master/libc/malloc_debug/README.md),
the option [record\_allocs](https://android.googlesource.com/platform/bionic/+/master/libc/malloc_debug/README.md#record_allocs_total_entries).
-To run these benchmarks, first copy the trace files to the target and
-unzip them using these commands:
+To run these benchmarks, first copy the trace files to the target using
+these commands:
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/traces/XXX.txt
- adb shell memory_replay32 /data/local/tmp/traces/XXX.txt
+ adb shell memory_replay64 /data/local/tmp/traces/XXX.zip
+ adb shell memory_replay32 /data/local/tmp/traces/XXX.zip
-Where XXX.txt is the name of a trace file.
+Where XXX.zip is the name of a zipped trace file. The `memory_replay`
+program also can process text files, but all trace files are currently
+checked in as zip files.
Every 100000 allocation operations, a dump of the RSS and VA space will be
performed. At the end, a final RSS and VA space number will be printed.