From: Vincent Fu <vincentfu@gmail.com>
To: Thomas Weber <thomas.weber@de.ibm.com>,
"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: fio version change gives different throughput results
Date: Wed, 6 Mar 2024 11:51:50 -0500 [thread overview]
Message-ID: <bf389657-7c37-4fe0-8ca7-17aecebfef3d@gmail.com> (raw)
In-Reply-To: <064bbd4dc5db416092090ce568ef8759744f46f0.camel@de.ibm.com>
On 3/6/24 04:44, Thomas Weber wrote:
<snip>
>
> Thank you. I noticed that fix as well in the fio changelog.
> From the description it seems to affect only non-sequential IO.
> However I saw huge throughput degradations for both rw=rw and
> rw=randrw.
>
> Do you think this is related to that bug fix too?
>
> [smallstuff-seq-slow]
> rw=rw
> nrfiles=1000
> openfiles=25
> filesize=1k-1m
> bssplit=4k/20:128k/80
> rwmixread=60
>
> [smallstuff-rand-slow]
> rw=randrw
> nrfiles=1000
> openfiles=25
> filesize=1k-1m
> bssplit=4k/50:8k/25:64k/25
> rwmixread=75
>
The patch description mentions file_service_type != sequential but makes
no comment about whether offsets are chosen randomly or sequentially. In
fact the example job in the patch description chooses offsets randomly.
I tried your smallstuff-seq-slow job and found the following:
fio-3.25+ [1]:----- 424 MiB/s read, 384 MiB/s write
fio-3.36:---------- 384 MiB/s read, 347 MiB/s write
fio-3.36-97-g9b699: 517 MiB/s read, 467 MiB/s write
[1] fio-3.25 needs 382975557e632efb506836bc1709789e615c9094 to build
with recent kernels
If you are able to reliably reproduce the problem I suggest that you run
git bisect to identify the commit responsible for the difference you
have observed.
Vincent
prev parent reply other threads:[~2024-03-06 16:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 13:53 fio version change gives different throughput results Thomas Weber
2024-03-05 17:11 ` Vincent Fu
2024-03-06 9:44 ` Thomas Weber
2024-03-06 16:51 ` Vincent Fu [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=bf389657-7c37-4fe0-8ca7-17aecebfef3d@gmail.com \
--to=vincentfu@gmail.com \
--cc=fio@vger.kernel.org \
--cc=thomas.weber@de.ibm.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