1IOshark is a repeatable application workload storage benchmark. You 2can find more documentation on IOshark at : 3https://docs.google.com/a/google.com/document/d/1Bhq7iNPVc_JzwRrkmZqcPjMvWgpHX0r3Ncq-ZsRNOBA/edit?usp=sharing 4 5The short summary of what IOshark is : IOshark has 2 components, one 6is a strace+ftrace compiler that takes straces and select ftraces fed 7into it and compiles this into bytecodes (stored in *.wl files). The 8compiler runs on a Linux host. The second component (which runs on the 9device) is the tester that takes as input the bytecode files (*.wl 10files) and executes them on the device. 11 12How to Run : 13---------- 14- First collect straces and compile these into bytecodes. The wrapper 15script provided (collect-straces.sh) collects straces, ships them to 16the host where the script runs, compiles and packages up the bytecode 17files into a wl.tar file. 18- Ship the wl.tar file and the iostark_bench binaries to the target 19device (on /data/local/tmp say). Explode the tarfile. 20- Run the tester. "ioshark_bench *.wl" runs the test with default 21options. Supported ioshark_bench options : 22-d : Preserve the delays between successive filesystem syscalls as 23seen in the original straces. 24-n <N> : Run for N iterations 25-t <N> : Limit to N threads. By default (without this option), IOshark 26will launch as many threads as there are input files, so 1 thread/file. 27-v : verbose. Chatty mode. 28-s : One line summary. 29-q : Don't create the files in read-only partitions like /system and 30/vendor. Instead do reads on those files. 31