9d00a124c5591198264ffedf0ba4c73bddfc346f |
|
09-Mar-2017 |
Mohan Srinivasan <srmohan@google.com> |
IOshark support to parse Linux filesystem ftraces. IOshark support to input filesystem ftracepooints (readpage(s)) to capture and replay mmap'ed IO (which aren't captured by strace). The new script collect-straces-ftraces.sh enables the necessary tracepoints, and collects ftraces and straces compiles these into intermediate bytecodes which ioshark_bench can then execute. Test: Generate several monkey based workloads, and use the script mentioned above to generate bytecodes and feed those into ioshark_bench. Change-Id: Iae57f5fdcdce0fedfd85c8d64ee006cc8b5b470d Signed-off-by: Mohan Srinivasan <srmohan@google.com>
/system/extras/ioshark/collect-straces.sh
|
02f8626d766424406bcfea1e20ef352d3b9a72cf |
|
25-Feb-2017 |
Mohan Srinivasan <srmohan@google.com> |
IOshark support to not pre-create files in /system, /vendor, ... 1) Add support to IOshark to not pre-create files that the workload read from /system, /vendor and other read-only partitions. Instead we just read the underlying files directly. 2) This support is implemented under a new -q (quick) mode. 3) Other misc fixes to do a setrlimit(NO_FD) so we don't run out of fds during test. 4) Also commiting raw strace files from several monkey runs so we can compile those if we make on disk IOshark format changes in the future. Test: Run IOshark with different workloads to make sure that this skipping of pre-creation works fine. Change-Id: Ic025cb0162eca479d9f529846e619dd4b71aa490 Signed-off-by: Mohan Srinivasan <srmohan@google.com>
/system/extras/ioshark/collect-straces.sh
|
b707f30a7cdd521db5d0d1c1e5c391e61a1675c9 |
|
20-Jan-2017 |
Mohan Srinivasan <srmohan@google.com> |
ioshark: A Repeatable Application Workload Storage Benchmark. ioshark is a repeatable application workload based storage benchmark. ioshark takes as input strace files, compiles them into bytecodes that you can then feed into the benchmark. This allows us to collect straces for a chosen application workload (by stracing zygote/zygote64), and use these to do A-B comparisons of storage features (anything including the filesystem and below, including new hardware). Test: Extra tests for ioshark aren't needed, ioshark reports detailed stats at the end of the run, which tells us whether the ioshark run was successful or not. In addition, we can strace ioshark_bench as it runs to make sure it is launching IOs as we would expect it to. Change-Id: I51fa9879dc11b526385eb7827ca2b4186662a463 Signed-off-by: Mohan Srinivasan <srmohan@google.com>
/system/extras/ioshark/collect-straces.sh
|
f2f5b6165a4b107f79a7e709f63fb66118a72477 |
|
19-Jan-2017 |
Mohan Srinivasan <srmohan@google.com> |
Revert "ioshark: A Repeatable Application Workload Based Storage Benchmark." (Broke the MacOS build - will commit after I test that this builds for MacOS). This reverts commit a5dc6d6fcab8dfe719c437e8a9111ba962df1c15. Change-Id: I53bc71eeb1bc3ad7706baae589cef8a80ef94c35
/system/extras/ioshark/collect-straces.sh
|
a5dc6d6fcab8dfe719c437e8a9111ba962df1c15 |
|
17-Jan-2017 |
Mohan Srinivasan <srmohan@google.com> |
ioshark: A Repeatable Application Workload Based Storage Benchmark. ioshark is a repeatable application storage workload benchmark. ioshark takes as input strace files, compiles them into bytecodes that you can then feed into the benchmark. This allows us to collect straces for a chosen application workload (by stracing zygote/zygote64), and use these to do A-B comparisons of storage features (anything including the filesystem and below, including new hardware). Test: Extra tests for ioshark aren't needed, ioshark reports detailed stats at the end of the run, which tells us whether the ioshark run was successful or not. In addition, we can strace ioshark_bench as it runs to make sure it is launching IOs as we would expect it to. Change-Id: I70674ff8daac229b9f8e5d37780f15c7a31a7ca0 Signed-off-by: Mohan Srinivasan <srmohan@google.com>
/system/extras/ioshark/collect-straces.sh
|
2716fdd9b83cc9b703d44fcc3baf456853c585cc |
|
22-Dec-2016 |
Jin Qian <jinqian@google.com> |
Revert "ioshark: A Repeatable Application Workload Based Storage Benchmark." This reverts commit 99c8f98f2a9c76fabb19cdbc5b495978cfc479b3. Change-Id: Id205f175802d55b8f12342f82199db5743e479dc
/system/extras/ioshark/collect-straces.sh
|
99c8f98f2a9c76fabb19cdbc5b495978cfc479b3 |
|
15-Dec-2016 |
Mohan Srinivasan <srmohan@google.com> |
ioshark: A Repeatable Application Workload Based Storage Benchmark. ioshark is a repeatable application storage workload benchmark. ioshark takes as input strace files, compiles them into bytecodes that you can then feed into the benchmark. This allows us to collect straces for a chosen application workload (by stracing zygote/zygote64), and use these to do A-B comparisons of storage features (anything including the filesystem and below, including new hardware). Test: Extra tests for ioshark aren't needed, ioshark reports detailed stats at the end of the run, which tells us whether the ioshark run was successful or not. In addition, we can strace ioshark_bench as it runs to make sure it is launching IOs as we would expect it to. Change-Id: Ieb0ecf5e32695ea95b361710aa31613f6ce63b97 Signed-off-by: Mohan Srinivasan <srmohan@google.com>
/system/extras/ioshark/collect-straces.sh
|