From: Jens Axboe <axboe@kernel.dk>
To: Nick dan <nickdan2999@gmail.com>, fio@vger.kernel.org
Subject: Re: Fio on Block size 128M
Date: Wed, 5 Jul 2023 11:05:11 -0600 [thread overview]
Message-ID: <ec7824a9-8d71-e1a8-eb87-23d9b5e9e235@kernel.dk> (raw)
In-Reply-To: <CAE6FHhHS5f5cs8SzfTfkaLRy=A7QS_q3QX2Tb3g3XDTaSXbE6Q@mail.gmail.com>
On 7/4/23 11:25?PM, Nick dan wrote:
> Hi
>
> I have a NVMe disk, SATA SSD and SATA HDD.
> I have mkfs.ext4 on all the disks. And mounted the file system on /mnt.
> I want the block size to be set as 128MB and file size 10GB
>
> What is the correct way to benchmark ? As it is taking a lot of time
> and the values of Throughput are not correct. What should be taken
> into consideration? Can you send the fio command?
What are you trying to do, specifically? A block size of 128MB should of
course work, but it's somewhat nonsensical as no applications would do
that, and on the device side, it'd be chopped into much smaller pieces
anyway. That means one fio read or write of 128MB would turn into
potentially many hundreds of device requests.
For any fio question or bug report, please include what you are seeing
and what you would expect. Just saying "it's taking a lot of time and
throughput is not correct" is not super useful, be more detailed and
specific. And as also stated in the REPORTING-BUGS file, include what
version you are running, the job file being used, etc. That would make
for a complete bug report.
--
Jens Axboe
parent reply other threads:[~2023-07-05 17:05 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAE6FHhHS5f5cs8SzfTfkaLRy=A7QS_q3QX2Tb3g3XDTaSXbE6Q@mail.gmail.com>]
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=ec7824a9-8d71-e1a8-eb87-23d9b5e9e235@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=nickdan2999@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).