From: Jens Axboe <axboe@kernel.dk>
To: Brian Fallik <bfallik@bamboom.com>
Cc: Jeff Moyer <jmoyer@redhat.com>,
"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: fio file test patterns
Date: Wed, 31 Aug 2011 15:38:24 -0600 [thread overview]
Message-ID: <4E5EA9D0.10109@kernel.dk> (raw)
In-Reply-To: <4E5EA5DF.5040609@fusionio.com>
On 2011-08-31 15:21, Jens Axboe wrote:
>> I also have another (maybe related?) question. Apologies if this
>> belongs in a separate thread, but are there any notes explaining why
>> fio lays out the files before starting sequential writes? The
>> workload I was hoping to simulate is sustained, sequential writes to
>> disk. I'm trying to answer the question "How many simultaneous
>> 200kBps writers can we support?" Using my current jobs file, fio
>> starts by creating the files (e.g "foo0: Laying out IO file(s) (1
>> file(s) / 4MB)") before it starts processing. However, creating the
>> files in advance accounts for a chunk of performance that doesn't seem
>> to be measured by fio. Am I misunderstanding how to configure fio or
>> its intended usage?
>
> You should be able to set overwrite=0 to avoid that. Are they random
> writes?
overwrite=0 is even default. I'm thinking the "Laying out IO file"
message is confusing, it wont actually write contents first unless you
ask it to (with eg overwrite=1).
--
Jens Axboe
next prev parent reply other threads:[~2011-08-31 21:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 17:53 fio file test patterns Brian Fallik
2011-08-31 18:30 ` Jeff Moyer
2011-08-31 19:56 ` Jens Axboe
2011-08-31 20:34 ` Brian Fallik
2011-08-31 21:21 ` Jens Axboe
2011-08-31 21:38 ` Jens Axboe [this message]
2011-09-01 14:18 ` Brian Fallik
2011-09-01 16:06 ` Jens Axboe
2011-09-01 18:17 ` Brian Fallik
2011-09-01 20:14 ` 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=4E5EA9D0.10109@kernel.dk \
--to=axboe@kernel.dk \
--cc=bfallik@bamboom.com \
--cc=fio@vger.kernel.org \
--cc=jmoyer@redhat.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