From: kernel test robot <oliver.sang@intel.com>
To: NeilBrown <neilb@suse.de>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>,
Chuck Lever <chuck.lever@oracle.com>,
Jeff Layton <jlayton@kernel.org>, <linux-nfs@vger.kernel.org>,
<oliver.sang@intel.com>
Subject: [linus:master] [nfsd] eccbbc7c00: dbench.max_latency 99.9% improvement
Date: Mon, 21 Apr 2025 13:44:18 +0800 [thread overview]
Message-ID: <202504211304.eb2ca0c2-lkp@intel.com> (raw)
Hello,
kernel test robot noticed a 99.9% improvement of dbench.max_latency on:
commit: eccbbc7c00a5aae5e704d4002adfaf4c3fa4b30d ("nfsd: don't use sv_nrthreads in connection limiting calculations.")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
testcase: dbench
config: x86_64-rhel-9.4
compiler: gcc-12
test machine: 224 threads 4 sockets Intel(R) Xeon(R) Platinum 8380H CPU @ 2.90GHz (Cooper Lake) with 192G memory
parameters:
nr_threads: 100%
cpufreq_governor: performance
disk: 1HDD
fs: btrfs
fs2: nfs
Details are as below:
-------------------------------------------------------------------------------------------------->
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250421/202504211304.eb2ca0c2-lkp@intel.com
=========================================================================================
compiler/cpufreq_governor/disk/fs2/fs/kconfig/nr_threads/rootfs/tbox_group/testcase:
gcc-12/performance/1HDD/nfs/btrfs/x86_64-rhel-9.4/100%/debian-12-x86_64-20240206.cgz/lkp-cpl-4sp2/dbench
commit:
de71d4e211 ("nfsd: fix legacy client tracking initialization")
eccbbc7c00 ("nfsd: don't use sv_nrthreads in connection limiting calculations.")
de71d4e211eddb67 eccbbc7c00a5aae5e704d4002ad
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
10:10 -100% :10 stderr.has_stderr
10:10 -100% :10 stderr.nfsproc3_create_3_failed_in_nfsio_create
%stddev %change %stddev
\ | \
71006 -99.9% 35.66 ± 7% dbench.max_latency
71006 -99.9% 35.66 ± 7% dbench.max_latency_harmonic_mean
1.11 +0.1 1.16 perf-stat.i.branch-miss-rate%
80903221 +6.3% 86014278 ± 2% perf-stat.i.branch-misses
1.10 +0.1 1.16 perf-stat.overall.branch-miss-rate%
79601951 +6.3% 84615085 ± 2% perf-stat.ps.branch-misses
Disclaimer:
Results have been estimated based on internal Intel analysis and are provided
for informational purposes only. Any difference in system hardware or software
design or configuration may affect actual performance.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-04-21 5:45 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=202504211304.eb2ca0c2-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=lkp@intel.com \
--cc=neilb@suse.de \
--cc=oe-lkp@lists.linux.dev \
/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