From: Wang Yugui <wangyugui@e16-tech.com>
To: linux-btrfs@vger.kernel.org
Subject: dbench (sync open) max_latency regression in btrfs 6.7.0
Date: Wed, 31 Jan 2024 15:06:32 +0800 [thread overview]
Message-ID: <20240131150632.A647.409509F4@e16-tech.com> (raw)
Hi,
I noticed a dbench max_latency regression in btrfs 6.7.0.
command:
dbench -s -t 60 -D /mnt/test 4
result of 6.6.15(rc1)
Operation Count AvgLat MaxLat
----------------------------------------
NTCreateX 430533 0.014 63.764
Close 316239 0.002 0.029
Rename 18242 0.080 0.340
Unlink 86967 0.047 0.396
Deltree 8 2.779 6.058
Mkdir 4 0.005 0.007
Qpathinfo 390364 0.007 0.105
Qfileinfo 68334 0.002 0.029
Qfsinfo 71601 0.003 0.037
Sfileinfo 35072 0.006 0.039
Find 150942 0.020 0.115
WriteX 214235 0.978 86.843
ReadX 675557 0.004 0.061
LockX 1406 0.004 0.019
UnlockX 1406 0.002 0.023
Flush 30182 0.013 3.074
Throughput 225.11 MB/sec (sync open) 4 clients 4 procs max_latency=86.861 ms
result of 6.7.0
Operation Count AvgLat MaxLat
----------------------------------------
NTCreateX 419186 0.013 0.266
Close 307908 0.002 0.046
Rename 17749 0.110 503.312
Unlink 84625 0.049 0.400
Deltree 8 3.125 7.249
Mkdir 4 0.004 0.004
Qpathinfo 380081 0.006 0.087
Qfileinfo 66545 0.002 0.030
Qfsinfo 69638 0.003 0.041
Sfileinfo 34131 0.006 0.043
Find 146925 0.019 0.114
WriteX 208546 1.007 536.773
ReadX 657303 0.004 0.042
LockX 1366 0.004 0.023
UnlockX 1366 0.002 0.015
Flush 29357 0.018 3.076
Throughput 218.935 MB/sec (sync open) 4 clients 4 procs max_latency=536.777 ms
This regession is firstly found on 6.8.0-rc2,
Now bisect-ed to 6.6.15(rc1) ~ 6.7.0. and more bisect work to do.
Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2024/01/31
reply other threads:[~2024-01-31 7:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240131150632.A647.409509F4@e16-tech.com \
--to=wangyugui@e16-tech.com \
--cc=linux-btrfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox