From: Jens Axboe <axboe@kernel.dk>
To: Elliott Balsley <elliott@altsystems.com>, fio <fio@vger.kernel.org>
Subject: Re: Setting number of read threads
Date: Wed, 26 Feb 2020 19:52:13 -0700 [thread overview]
Message-ID: <02eb7f85-72ab-f311-22fe-832a140bb2e6@kernel.dk> (raw)
In-Reply-To: <CABO+gV_6uBVxzzZ3K4HmDs18w_KzT8C5QxsNgLN3wp1C=x7NwQ@mail.gmail.com>
On 2/26/20 2:32 PM, Elliott Balsley wrote:
> When I do a sequential read test with multiple threads, the initial
> write only uses one thread. Is there some way to adjust this? For
> example a command like this:
>
> fio --name moe --rw read --directory /mnt/nv01/fio/local --size 40G
> --bs 4M --numjobs 4 --group_reporting --direct 1
>
> It lays out four files one at a time, then it reads them all back at
> once. I would like to lay out the four files simultaneously to save
> time. I hope this makes sense; I'm not sure if I'm phrasing this in
> the right way.
create_serialize=false would do that. It defaults to sequentially
since otherwise the fs layout tends to suffer.
--
Jens Axboe
prev parent reply other threads:[~2020-02-27 2:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 21:32 Setting number of read threads Elliott Balsley
2020-02-27 2:52 ` 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=02eb7f85-72ab-f311-22fe-832a140bb2e6@kernel.dk \
--to=axboe@kernel.dk \
--cc=elliott@altsystems.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.