From: Saeed <ionictea@gmail.com>
To: fio@vger.kernel.org
Subject: write_iops_log doesn't show any iops
Date: Mon, 22 Aug 2016 11:27:45 -0500 [thread overview]
Message-ID: <npf960$31m$1@blaine.gmane.org> (raw)
1, 1, 1, 4096
1, 1, 1, 4096
1, 1, 1, 4096
1, 1, 1, 4096
1, 1, 1, 4096
1, 1, 1, 4096
1, 1, 1, 4096
1, 1, 1, 4096
1, 1, 1, 4096
2, 1, 1, 4096
2, 1, 1, 4096
2, 1, 1, 4096
2, 1, 1, 4096
2, 1, 1, 4096
2, 1, 1, 4096
2, 1, 1, 4096
Strange but my write_iops_log log file doesn't contain any IOP data.
What column should the iops data be in and what could be the reason why
I'm getting any iop stats?
1, 1, 1, 4096
1, 1, 1, 4096
1, 1, 1, 4096
1, 1, 1, 4096
1, 1, 1, 4096
1, 1, 1, 4096
1, 1, 1, 4096
1, 1, 1, 4096
1, 1, 1, 4096
1, 1, 1, 4096
2, 1, 1, 4096
2, 1, 1, 4096
2, 1, 1, 4096
2, 1, 1, 4096
2, 1, 1, 4096
2, 1, 1, 4096
2, 1, 1, 4096
2, 1, 1, 4096
FIO 2.12 job:
[global]
ioengine=libaio
direct=1
filename=/dev/sdc
group_reporting
numjobs=1
time_based=1
per_job_logs=0
write_bw_log=results
write_iops_log=results
write_lat_log=results
[fill]
rw=randwrite
bs=8K
runtime=120
iodepth=1
stonewall
[read]
rw=randread
bs=8k
iodepth=16
runtime=480
stonewall
next reply other threads:[~2016-08-22 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 16:27 Saeed [this message]
2016-08-22 17:32 ` write_iops_log doesn't show any iops Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='npf960$31m$1@blaine.gmane.org' \
--to=ionictea@gmail.com \
--cc=fio@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.