From: Jens Axboe <axboe@kernel.dk>
To: Suresh Dhanarajan <sureshdrajan@gmail.com>
Cc: fio@vger.kernel.org
Subject: Re: Issue with verify and Mix read/writes
Date: Thu, 19 Apr 2012 09:46:45 +0200 [thread overview]
Message-ID: <4F8FC2E5.1000207@kernel.dk> (raw)
In-Reply-To: <CAN8qX8busH4Nu=0BuAYxeMOJSp+PC_z5JK3LPLaGAzb3Wy_Oug@mail.gmail.com>
On 04/19/2012 12:14 AM, Suresh Dhanarajan wrote:
> Hi Jens,
>
> I am using the verify option with mix read and write case.
> When verify option is I am seeing that the results are not reflecting
> the actual percentage given in the jobfile.
> When i don't use verify option the results are exactly as per the
> percentage given in the jobfile.
>
> Please fin the result for various cases with and without verify option,
>
> withverify sequential :-
> Total IO (KB), bandwidth (KB/sec), IOPS, runtime (msec)
> 2988;2436;594;1256
> 10240;6565;1603;1597
> ===================
> wthoutverify sequential :-
> Total IO (KB), bandwidth (KB/sec), IOPS, runtime (msec)
> 3124;2460;600;1300
> 7116;5605;1368;1300
> ===================
>
> random with verify
> Total IO (KB), bandwidth (KB/sec), IOPS, runtime (msec)
> 3088;431;105;7322
> 10240;1363;332;7693
> ===============
>
> random without verify
> Total IO (KB), bandwidth (KB/sec), IOPS, runtime (msec)
> 3076;430;105;7311
> 7164;1003;244;7311
>
> I used 70% read and 30% write option.
> Is it that when verify is used the mix percentage wont be honored?
> I had mentioned size has 10mb but when verify is used even that is not
> getting honored.
> Is there a way to make this case to honor the percentage set in the job file?
The reads that are done to verify a written block are not accounted in
the read/write mix ratio. So that is why you see more reads than you
asked for.
--
Jens Axboe
prev parent reply other threads:[~2012-04-19 7:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 22:14 Issue with verify and Mix read/writes Suresh Dhanarajan
2012-04-19 7:46 ` Jens Axboe [this message]
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=4F8FC2E5.1000207@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=sureshdrajan@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox