All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Sang <oliver.sang@intel.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Jeff Layton <jlayton@kernel.org>,
	Mike Snitzer <snitzer@redhat.com>,
	"oe-lkp@lists.linux.dev" <oe-lkp@lists.linux.dev>,
	"lkp@intel.com" <lkp@intel.com>, <oliver.sang@intel.com>
Subject: Re: [snitzer:cel-nfsd-next-6.12-rc5] [nfsd] b4be3ccf1c: fsmark.app_overhead 92.0% regression
Date: Thu, 19 Dec 2024 10:32:31 +0800	[thread overview]
Message-ID: <Z2OFv5DMu8ZzPrac@xsang-OptiPlex-9020> (raw)
In-Reply-To: <1e5c1ecd-7910-4033-a43a-c32007be55a3@oracle.com>

hi, Chuck Lever,

On Mon, Dec 16, 2024 at 05:23:48PM -0500, Chuck Lever wrote:
> On 12/5/24 9:33 PM, Oliver Sang wrote:
> > hi, Chuck Lever,
> > 
> > On Thu, Dec 05, 2024 at 10:37:10AM -0500, Chuck Lever wrote:
> > 
> > [...]
> > 
> > > 
> > > Earlier this week I thought I had the full set of patches to
> > > test and could just apply them on v6.13-rc1, but it turns out
> > > that I don't have them all yet. There are one or two that I
> > > broke while trying to prepare for v6.12, and I've misplaced
> > > Jeff's originals.
> > > 
> > > I will let you know when that branch is ready for a retest.
> > > Sorry for the noise!
> > 
> > Not at all! always our great pleasure that we can supply any help.
> > 
> > got it. just wait your notification. thanks!
> 
> The series currently in the nfsd-testing branch is complete and stable
> enough for you to benchmark.

FYI. we compared the branch tip with v6.13-rc3, the fsmark.app_overhead
regression are less now. while fsmark.files_per_sec keeps not being impacted.

if bisect can succeed to spot out one commit, we will also send out a report.

=========================================================================================
compiler/cpufreq_governor/disk/filesize/fs2/fs/iterations/kconfig/nr_files_per_directory/nr_threads/rootfs/sync_method/tbox_group/test_size/testcase:
  gcc-12/performance/1HDD/4K/nfsv4/btrfs/1x/x86_64-rhel-9.4/1fpd/1t/debian-12-x86_64-20240206.cgz/fsyncBeforeClose/lkp-icl-2sp6/40M/fsmark

commit:
  v6.13-rc3
  8d5b7358ea7c0 ("nfsd: add shrinker to reduce number of slots allocated per session")

       v6.13-rc3 8d5b7358ea7c07b69c44f0af21e
---------------- ---------------------------
         %stddev     %change         %stddev
             \          |                \
   2790150 ± 52%     -60.6%    1099116 ±120%  numa-meminfo.node1.FilePages
    697551 ± 52%     -60.6%     274783 ±120%  numa-vmstat.node1.nr_file_pages
      1176 ± 71%   +2210.3%      27185 ±247%  sched_debug.cpu.max_idle_balance_cost.stddev
      2882            -7.1%       2677        vmstat.system.cs
   3064384           +57.8%    4834169        fsmark.app_overhead
     18.58            -0.2%      18.54        fsmark.files_per_sec
     53429           -17.3%      44169        fsmark.time.voluntary_context_switches
      2805            -7.4%       2598        perf-stat.i.context-switches
      2800            -7.4%       2594        perf-stat.ps.context-switches
   1750049            -1.2%    1729157        proc-vmstat.numa_hit
   1617582            -1.3%    1596589        proc-vmstat.numa_local
      2.03 ±  2%      +5.5%       2.14        time.system_time
     53429           -17.3%      44169        time.voluntary_context_switches
      0.80 ± 11%      -0.3        0.52 ± 56%  perf-profile.calltrace.cycles-pp.tcp_write_xmit.__tcp_push_pending_frames.tcp_sendmsg_locked.tcp_sendmsg.sock_sendmsg
      0.80 ± 11%      -0.2        0.59 ± 39%  perf-profile.calltrace.cycles-pp.__tcp_push_pending_frames.tcp_sendmsg_locked.tcp_sendmsg.sock_sendmsg.svc_tcp_sendmsg
      0.39 ± 23%      -0.2        0.19 ± 53%  perf-profile.children.cycles-pp.__close
      0.39 ± 20%      -0.2        0.20 ± 47%  perf-profile.children.cycles-pp.__x64_sys_close
      0.14 ± 15%      -0.1        0.06 ± 79%  perf-profile.children.cycles-pp.syscall_return_via_sysret

> 
> 
> -- 
> Chuck Lever

      reply	other threads:[~2024-12-19  2:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-07  4:55 [snitzer:cel-nfsd-next-6.12-rc5] [nfsd] b4be3ccf1c: fsmark.app_overhead 92.0% regression kernel test robot
2024-11-07 11:35 ` Jeff Layton
2024-11-13 15:48   ` Chuck Lever
2024-11-13 16:10     ` Jeff Layton
2024-11-13 16:14       ` Chuck Lever
2024-11-13 16:20         ` Jeff Layton
2024-11-13 16:37           ` Chuck Lever III
2024-11-13 17:02             ` Jeff Layton
2024-11-14 14:37 ` Chuck Lever
2024-11-18  7:53   ` Oliver Sang
2024-12-02 15:40     ` Chuck Lever III
2024-12-03  5:01       ` Oliver Sang
2024-12-03 14:54         ` Chuck Lever III
2024-12-05  7:27           ` Oliver Sang
2024-12-05 14:15             ` Jeff Layton
2024-12-05 15:37             ` Chuck Lever
2024-12-06  2:33               ` Oliver Sang
2024-12-16 22:23                 ` Chuck Lever
2024-12-19  2:32                   ` Oliver Sang [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=Z2OFv5DMu8ZzPrac@xsang-OptiPlex-9020 \
    --to=oliver.sang@intel.com \
    --cc=chuck.lever@oracle.com \
    --cc=jlayton@kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=snitzer@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.