From: Jens Axboe <axboe@kernel.dk>
To: Srinivasa Chamarthy <chamarthy.raju@gmail.com>, fio@vger.kernel.org
Subject: Re: achieving a workload to get specific unique duplicate blocks
Date: Mon, 04 May 2015 14:39:15 -0600 [thread overview]
Message-ID: <5547D8F3.6090408@kernel.dk> (raw)
In-Reply-To: <CABtFm2U5t2=sM4MDKhaPn7n9nsJTSBUCSUeZ=9irt8EEBTogBQ@mail.gmail.com>
On 04/25/2015 07:03 AM, Srinivasa Chamarthy wrote:
> Firstly, thanks before in hand. :)
>
> Using FIO, what is the way to achieve a work load with specific number
> of unique blocks duplicates for specific number of times. For Example,
> i want a 252k block duplicates 1000 times and i want it to be the
> unique block in the complete workload.
If you have very specific requirements, it might be easier to simply
write an iolog generator that spits out what you want the pattern to
look like. Then fio can import that, and run the workload.
> Another query is that, for a blocksize of 256k does the io buffers are
> created at 256k and written to the disk and are all those 256k blocks
> unique buffer?. Can there be a change that in a 256k block, the
> smaller size buffers be the same?
That depends on the settings for compressibility, dedupability, etc. In
general see scramble_buffers, refill_buffers, and so on. That is all in
the man page or HOWTO.
--
Jens Axboe
next prev parent reply other threads:[~2015-05-04 20:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-25 13:03 achieving a workload to get specific unique duplicate blocks Srinivasa Chamarthy
2015-05-04 20:39 ` Jens Axboe [this message]
2015-05-05 2:23 ` Srinivasa Chamarthy
2015-05-07 2:19 ` Matthew Eaton
2015-05-07 3:58 ` Srinivasa Chamarthy
2015-05-07 6:32 ` Srinivasa Chamarthy
2015-05-07 14:27 ` Jens Axboe
2015-05-07 15:30 ` Srinivasa Chamarthy
2015-05-08 9:35 ` Srinivasa Chamarthy
2015-05-08 6:04 ` Ruvinsky, Konstantin
2015-05-08 6:10 ` Ruvinsky, Konstantin
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=5547D8F3.6090408@kernel.dk \
--to=axboe@kernel.dk \
--cc=chamarthy.raju@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.