From: Jens Axboe <jaxboe@fusionio.com>
To: Spelic <spelic@shiftmail.org>
Cc: fio@vger.kernel.org
Subject: Re: Suggestion on size= and test length
Date: Mon, 3 Jan 2011 12:04:35 +0100 [thread overview]
Message-ID: <4D21AD43.3090200@fusionio.com> (raw)
In-Reply-To: <4D1FFB19.7020202@shiftmail.org>
On 2011-01-02 05:12, Spelic wrote:
> Dear fio developers,
>
> Thanks for the very good application, but may I suggest that the size=
> option controls only the size of the files used for the test (in
> particular random r/w tests), while there should be another option
> totaltransfer= which controls how long is the test? And/or a walltime=
> option to make the test length time based... even better!
>
> Currently we either are hit by short seeks (size= small) or have to
> wait for impossibly long tests uselessly (size= large).
What about just adding a runtime= setting to shorten the run? Use the
full size, but put a cap on runtime.
--
Jens Axboe
prev parent reply other threads:[~2011-01-03 11:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-02 4:12 Suggestion on size= and test length Spelic
2011-01-03 11:04 ` 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=4D21AD43.3090200@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=fio@vger.kernel.org \
--cc=spelic@shiftmail.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