| Age | Commit message (Collapse) | Author |
|---|
|
Make IOshark portable across 32-bit and 64-bit devices, as well as
little endian and big endian architectures. This is achieved by
locking down the on-disk format of IOshark workload files. We can now
generate the workload files on a 64-bit host and use those workload
files to run the benchmark on a 32-bit userspace device (such as
fugu). The change also has minor fixes to make IOshark work on taimen
and walleye.
Test: Test across 64- and 32-bit devices. Generate workload files on a
64 bit device and test on 32-bit devices (as well as 64-bit devices).
Change-Id: I700ca5ae0da0ab029d977c906a63f1cd20a78a14
Signed-off-by: Mohan Srinivasan <srmohan@google.com>
|
|
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>
|
|
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>
|
|
Benchmark." (Broke the MacOS build - will commit after I test that this builds for MacOS).
This reverts commit a5dc6d6fcab8dfe719c437e8a9111ba962df1c15.
Change-Id: I53bc71eeb1bc3ad7706baae589cef8a80ef94c35
|
|
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>
|
|
This reverts commit 99c8f98f2a9c76fabb19cdbc5b495978cfc479b3.
Change-Id: Id205f175802d55b8f12342f82199db5743e479dc
|
|
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>
|
