On Tue, Nov 03, 2020 at 11:53:39AM +0800, Wu Fengguang wrote:
On Tue, Nov 03, 2020 at 11:36:03AM +0800, Lu Kaiyi wrote:
[why] avoid explosion of parameter for iozone-bs.yaml
Signed-off-by: Lu Kaiyi 2392863668@qq.com
jobs/iozone-bs.yaml | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/jobs/iozone-bs.yaml b/jobs/iozone-bs.yaml index e2cd9f48..f9ab305f 100644 --- a/jobs/iozone-bs.yaml +++ b/jobs/iozone-bs.yaml @@ -2,9 +2,7 @@ suite: iozone category: benchmark
file_size: 4g -write_rewrite: true -read_reread: true -random_read_write: true +test: write_rewrite,read_reread,random_read_write
Looks good. Though write_rewrite might be simplified to "write" and
read_reread => read random_read_write => rand_rw
the output like below:
Record Size 16384 kB File size set to 4194304 kB Command line used: iozone -r 16m -s 4g -i 0 -i 1 -i 2 -f /fs/sda/iozonetest Output is in kBytes/sec ... random random bkwd record stride kB reclen write rewrite read reread read write read rewrite read fwrite frewrite fread freread 4194304 16384 5843739 5917648 5480193 5455472 5474684 5941833
for -i 0, correspond to the result write and rewrite. for -i 1, correspond to the result read and reread.
if use test name like below:
write_rewrite => write read_reread => read
maybe the test name not exactly accurate.
Thanks, Kaiyi
Thanks, Fengguang