From: Wang Yugui <wangyugui@e16-tech.com>
To: linux-xfs@vger.kernel.org
Subject: performance regression between 6.1.x and 5.15.x
Date: Mon, 08 May 2023 17:24:07 +0800 [thread overview]
Message-ID: <20230508172406.1CF3.409509F4@e16-tech.com> (raw)
Hi,
I noticed a performance regression of xfs 6.1.27/6.1.23,
with the compare to xfs 5.15.110.
It is yet not clear whether it is a problem of xfs or lvm2.
any guide to troubleshoot it?
test case:
disk: NVMe PCIe3 SSD *4
LVM: raid0 default strip size 64K.
fio -name write-bandwidth -rw=write -bs=1024Ki -size=32Gi -runtime=30
-iodepth 1 -ioengine sync -zero_buffers=1 -direct=0 -end_fsync=1 -numjobs=4
-directory=/mnt/test
6.1.27/6.1.23
fio bw=2623MiB/s (2750MB/s)
perf report:
Samples: 330K of event 'cycles', Event count (approx.): 120739812790
Overhead Command Shared Object Symbol
31.07% fio [kernel.kallsyms] [k] copy_user_enhanced_fast_string
5.11% fio [kernel.kallsyms] [k] iomap_set_range_uptodate.part.24
3.36% fio [kernel.kallsyms] [k] asm_exc_nmi
3.29% fio [kernel.kallsyms] [k] native_queued_spin_lock_slowpath
2.27% fio [kernel.kallsyms] [k] iomap_write_begin
2.18% fio [kernel.kallsyms] [k] get_page_from_freelist
2.11% fio [kernel.kallsyms] [k] xas_load
2.10% fio [kernel.kallsyms] [k] xas_descend
5.15.110
fio bw=6796MiB/s (7126MB/s)
perf report:
Samples: 267K of event 'cycles', Event count (approx.): 186688803871
Overhead Command Shared Object Symbol
38.09% fio [kernel.kallsyms] [k] copy_user_enhanced_fast_string
6.76% fio [kernel.kallsyms] [k] iomap_set_range_uptodate
4.40% fio [kernel.kallsyms] [k] xas_load
3.94% fio [kernel.kallsyms] [k] get_page_from_freelist
3.04% fio [kernel.kallsyms] [k] asm_exc_nmi
1.97% fio [kernel.kallsyms] [k] native_queued_spin_lock_slowpath
1.88% fio [kernel.kallsyms] [k] __pagevec_lru_add
1.53% fio [kernel.kallsyms] [k] iomap_write_begin
1.53% fio [kernel.kallsyms] [k] __add_to_page_cache_locked
1.41% fio [kernel.kallsyms] [k] xas_start
Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2023/05/08
next reply other threads:[~2023-05-08 9:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 9:24 Wang Yugui [this message]
2023-05-08 14:46 ` performance regression between 6.1.x and 5.15.x Wang Yugui
2023-05-08 22:32 ` Dave Chinner
2023-05-08 23:25 ` Wang Yugui
2023-05-09 1:36 ` Dave Chinner
2023-05-09 12:37 ` Wang Yugui
2023-05-09 22:14 ` Dave Chinner
2023-05-10 5:46 ` Wang Yugui
2023-05-10 7:27 ` Dave Chinner
2023-05-10 8:50 ` Wang Yugui
2023-05-11 1:34 ` Dave Chinner
2023-05-17 13:07 ` Wang Yugui
2023-05-17 22:11 ` Dave Chinner
2023-05-18 18:36 ` Creating large folios in iomap buffered write path Matthew Wilcox
2023-05-18 21:46 ` Matthew Wilcox
2023-05-18 22:03 ` Matthew Wilcox
2023-05-19 2:55 ` Wang Yugui
2023-05-19 15:38 ` Matthew Wilcox
2023-05-20 13:35 ` Wang Yugui
2023-05-20 16:35 ` Matthew Wilcox
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=20230508172406.1CF3.409509F4@e16-tech.com \
--to=wangyugui@e16-tech.com \
--cc=linux-xfs@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;
as well as URLs for NNTP newsgroup(s).