From: "Neto, Antonio Jose Rodrigues" <Antonio.Jose.Rodrigues.Neto@netapp.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Helping to model this workload
Date: Fri, 26 Jul 2013 14:22:20 +0000 [thread overview]
Message-ID: <CE17FDFB.12F1B%Antonio.Jose.Rodrigues.Neto@netapp.com> (raw)
In-Reply-To: <CE16F954.12DA8%Antonio.Jose.Rodrigues.Neto@netapp.com>
>>>>>
>>>>>Just to confirm..
>>>>>
>>>>> bs_is_seq_rand=1
>>>>>
>>>>> bs=64k,4k
>>>>>
>>>>> It's 64K for sequential and 4K for random
>>>>>
>>>>> Right?
>>>>
>>>> Correct. If bs_is_seq_rand is set, any READ block size setting is
>>>> applied to sequential IO, and any WRITE block size setting is applied
>>>>to
>>>> random IO.
>>>>
>>>> --
>>>> Jens Axboe
>>>>
>>>
>>> Let me see if I understood:
>>>
>>> But Jens, if I want sequential read AND write 64KB and random read AND
>>> write 4KB?
>>
>>Then you'd do:
>>
>>bs=64k,4k
>>bs_is_seq_rand=1
>>
>>any ANY sequential IO will be 64kb, and ANY random IO will be 4kb.
>>
>>--
>>Jens Axboe
>>
>
>This?
>
>[workload]
>bs=64k,4k
>
>bs_is_seq_rand=1
>
>ioengine=libaio
>iodepth=2
>numjobs=64
>direct=1
>runtime=2400
>size=2000g
>filename=\\.\PhysicalDrive9:\\.\PhysicalDrive10
>rw=randrw
>rwmixread=85
>percentage_random=59,67
>thread
>unified_rw_reporting=1
>group_reporting=1
Jens
Would be nice if we could specify?
Iodepth for sequential and random
Numjobs for sequential and random (for example: I would like to have 16
jobs doing random and 1 job only doing sequential)
Thanks for considering it in the future
All the best my friend
neto
next prev parent reply other threads:[~2013-07-26 14:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CE142CC7.127F5%Antonio.Jose.Rodrigues.Neto@netapp.com>
2013-07-23 16:52 ` Helping to model this workload Neto, Antonio Jose Rodrigues
2013-07-25 16:45 ` Jens Axboe
2013-07-25 16:52 ` Neto, Antonio Jose Rodrigues
2013-07-25 18:27 ` Jens Axboe
2013-07-25 18:31 ` Neto, Antonio Jose Rodrigues
2013-07-25 18:42 ` Jens Axboe
2013-07-25 18:59 ` Neto, Antonio Jose Rodrigues
2013-07-25 19:02 ` Jens Axboe
2013-07-25 19:02 ` Neto, Antonio Jose Rodrigues
2013-07-25 19:03 ` Jens Axboe
2013-07-25 19:07 ` Neto, Antonio Jose Rodrigues
2013-07-25 19:11 ` Jens Axboe
2013-07-25 19:50 ` Neto, Antonio Jose Rodrigues
2013-07-26 14:22 ` Neto, Antonio Jose Rodrigues [this message]
2013-07-26 14:24 ` Jens Axboe
2013-07-26 14:28 ` Neto, Antonio Jose Rodrigues
2013-07-26 14:34 ` Jens Axboe
2013-07-26 14:35 ` Neto, Antonio Jose Rodrigues
2013-07-26 14:39 ` Neto, Antonio Jose Rodrigues
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=CE17FDFB.12F1B%Antonio.Jose.Rodrigues.Neto@netapp.com \
--to=antonio.jose.rodrigues.neto@netapp.com \
--cc=axboe@kernel.dk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox