linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Shakeel Butt <shakeel.butt@linux.dev>
To: Oliver Sang <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
	Linux Memory Management List <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Yosry Ahmed <yosryahmed@google.com>,
	"T.J. Mercier" <tjmercier@google.com>,
	Roman Gushchin <roman.gushchin@linux.dev>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Michal Hocko <mhocko@kernel.org>,
	Muchun Song <muchun.song@linux.dev>,
	cgroups@vger.kernel.org, ying.huang@intel.com,
	feng.tang@intel.com, fengwei.yin@intel.com
Subject: Re: [linux-next:master] [memcg]  70a64b7919: will-it-scale.per_process_ops -11.9% regression
Date: Sun, 19 May 2024 20:49:33 -0700	[thread overview]
Message-ID: <20240520034933.wei3dffiuhq7uxhv@linux.dev> (raw)
In-Reply-To: <Zkq41w8YKCaKQAGk@xsang-OptiPlex-9020>

On Mon, May 20, 2024 at 10:43:35AM +0800, Oliver Sang wrote:
> hi, Shakeel,
> 
> On Sun, May 19, 2024 at 10:20:28AM -0700, Shakeel Butt wrote:
> > On Sun, May 19, 2024 at 05:14:39PM +0800, Oliver Sang wrote:
> > > hi, Shakeel,
> > > 
> > > On Fri, May 17, 2024 at 11:28:10PM -0700, Shakeel Butt wrote:
> > > > On Fri, May 17, 2024 at 01:56:30PM +0800, kernel test robot wrote:
> > > > > 
> > > > > 
> > > > > Hello,
> > > > > 
> > > > > kernel test robot noticed a -11.9% regression of will-it-scale.per_process_ops on:
> > > > > 
> > > > > 
> > > > > commit: 70a64b7919cbd6c12306051ff2825839a9d65605 ("memcg: dynamically allocate lruvec_stats")
> > > > > https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
> > > > > 
> > > > 
> > > > Thanks for the report. Can you please run the same benchmark but with
> > > > the full series (of 8 patches) or at least include the ff48c71c26aa
> > > > ("memcg: reduce memory for the lruvec and memcg stats").
> > > 
> > > while this bisect, ff48c71c26aa has been checked. it has silimar data as
> > > 70a64b7919 (a little worse actually)
> > > 
> > > 59142d87ab03b8ff 70a64b7919cbd6c12306051ff28 ff48c71c26aaefb090c108d8803
> > > ---------------- --------------------------- ---------------------------
> > >          %stddev     %change         %stddev     %change         %stddev
> > >              \          |                \          |                \
> > >      91713           -11.9%      80789           -13.2%      79612        will-it-scale.per_process_ops
> > > 
> > > 
> > > ok, we will run tests on tip of the series which should be below if I understand
> > > it correctly.
> > > 
> > > * a94032b35e5f9 memcg: use proper type for mod_memcg_state
> > > 
> > > 
> > 
> > Thanks a lot Oliver. One question: what is the filesystem mounted at
> > /tmp on your test machine? I just wanted to make sure I run the test
> > with minimal changes from your setup.
> 
> we don't have specific partition for /tmp, just use tmpfs
> 
> tmp on /tmp type tmpfs (rw,relatime)
> 
> 
> BTW, the test on a94032b35e5f9 finished, still have similar score to 70a64b7919
> 
> =========================================================================================
> compiler/cpufreq_governor/kconfig/mode/nr_task/rootfs/tbox_group/test/testcase:
>   gcc-13/performance/x86_64-rhel-8.3/process/100%/debian-12-x86_64-20240206.cgz/lkp-skl-fpga01/page_fault2/will-it-scale
> 
> 59142d87ab03b8ff 70a64b7919cbd6c12306051ff28 ff48c71c26aaefb090c108d8803 a94032b35e5f97dc1023030d929
> ---------------- --------------------------- --------------------------- ---------------------------
>          %stddev     %change         %stddev     %change         %stddev     %change         %stddev
>              \          |                \          |                \          |                \
>      91713           -11.9%      80789           -13.2%      79612           -13.0%      79833        will-it-scale.per_process_ops
> 

Thanks again. I am not sure if you have a single node machine but if you
have, can you try to repro this issue on such machine. At the moment, I
don't have access to such machine but I will try to repro myself as
well.

Shakeel


  reply	other threads:[~2024-05-20  3:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-17  5:56 kernel test robot
2024-05-17 23:38 ` Yosry Ahmed
2024-05-18  6:28 ` Shakeel Butt
2024-05-19  9:14   ` Oliver Sang
2024-05-19 17:20     ` Shakeel Butt
2024-05-20  2:43       ` Oliver Sang
2024-05-20  3:49         ` Shakeel Butt [this message]
2024-05-21  2:43           ` Oliver Sang
2024-05-22  4:18             ` Shakeel Butt
2024-05-23  7:48               ` Oliver Sang
2024-05-23 16:47                 ` Shakeel Butt
2024-05-24  7:45                   ` Oliver Sang
2024-05-24 18:06                     ` Shakeel Butt
2024-05-28  6:30                       ` Shakeel Butt
2024-05-30  6:17                         ` Oliver Sang

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=20240520034933.wei3dffiuhq7uxhv@linux.dev \
    --to=shakeel.butt@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=cgroups@vger.kernel.org \
    --cc=feng.tang@intel.com \
    --cc=fengwei.yin@intel.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=mhocko@kernel.org \
    --cc=muchun.song@linux.dev \
    --cc=oe-lkp@lists.linux.dev \
    --cc=oliver.sang@intel.com \
    --cc=roman.gushchin@linux.dev \
    --cc=tjmercier@google.com \
    --cc=ying.huang@intel.com \
    --cc=yosryahmed@google.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