The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Aaron Lu <aaron.lu@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Deng Pan <pan.deng@intel.com>, <tim.c.chen@intel.com>,
	<vincent.guittot@linaro.org>, <linux-kernel@vger.kernel.org>,
	<tianyou.li@intel.com>, <yu.ma@intel.com>, <lipeng.zhu@intel.com>,
	<yu.c.chen@intel.com>, Tim Chen <tim.c.chen@linux.intel.com>
Subject: Re: [PATCH v2] sched/task_group: Re-layout structure to reduce false sharing
Date: Fri, 30 Jun 2023 17:35:00 +0800	[thread overview]
Message-ID: <20230630093500.GA579792@ziqianlu-dell> (raw)
In-Reply-To: <20230628051419.GA565419@ziqianlu-dell>

On Wed, Jun 28, 2023 at 01:18:34PM +0800, Aaron Lu wrote:
> On Tue, Jun 27, 2023 at 12:14:37PM +0200, Peter Zijlstra wrote:
> > and can we still measure an improvement over this with that approach?
> 
> Let me re-run those tests and see how things change.
> 
> In my previous tests I didn't turn on CONFIG_RT_GROUP_SCHED. To test
> this, I suppose I'll turn CONFIG_RT_GROUP_SCHED on and apply this change
> here that made tg->load_avg in a dedicated cacheline, then see how
> performances change with the "Make tg->load_avg per node" patch. Will
> report back once done.

The test summary is:
- On 2sockets/112cores/224threads SPR, it's still overall a win.
  Transactions of postgres_sysbench improved 47.7%, hackbench improved
  13.5% and netperf improved 39.5%;
- On 2sockets/64cores/128threads Icelake, hackbench and netperf have
  improvement while postgres_sysbench transaction slightly dropped.
  hackbench improved 6.2%, netperf improved 20.3% and transactions of
  postgres_sysbench dropped 1.2%;
- On 2sockets/48cores/96threads CascadeLake, hackbench and netperf are
  roughly flat.

Below are detailed results:

SPR: 2socket/112cores/224threads

postgres_sysbench/1instance/100%(nr_client=nr_cpu)
kernel          transactions(higher is better)
aligned         89623.85±0.35%
per_node       132401.37±0.83%

hackbench/pipe/threads
kernel          time(less is better)
aligned         47.43±0.48%
per_node        41.02±0.69%

netperf/UDP_RR/100%(nr_client=nr_cpu)
kernel          throughput(higher is better)
aligned          9415.97±3.81%
per_node        13131.24±2.67%

ICL: 2sockets/64cores/128threads

postgres_sysbench/1instance/75%
kernel         transactions
aligned        62291.58±0.64%
per_node       61561.40±0.39%

hackbench/pipe/threads
kernel         time
aligned        41.66±0.04%
per_node       39.07±0.36%

netperf/UDP_RR/100%
kernel         throughput
aligned        21365.01±3.32%
per_node       25692.05±2.03%

CSL: 2sockets/48cores/96threads

hackbench/pipe/threads
kernel          time
aligned:        48.78±0.61%
per_node:       48.95±1.06

netperf/UDP_RR/100%
kernel         throughput
aligned        25853.82±11.46%
per_node       25264.38±0.85%

I think I'll spin a new version for the "Make tg->load_avg per-node"
patch with all the information I collected.

      reply	other threads:[~2023-06-30  9:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-21  8:14 [PATCH v2] sched/task_group: Re-layout structure to reduce false sharing Deng Pan
2023-06-26  5:47 ` Aaron Lu
2023-06-26  7:52   ` Chen Yu
2023-06-26 12:53     ` Aaron Lu
2023-06-27  8:05       ` Chen Yu
2023-06-27 10:10       ` Peter Zijlstra
2023-06-26 17:09     ` Tim Chen
2023-06-27  8:08       ` Chen Yu
2023-06-27 14:52         ` Deng, Pan
2023-06-26 12:51   ` Deng, Pan
2023-06-27 10:14   ` Peter Zijlstra
2023-06-27 16:12     ` Deng, Pan
2023-07-06 14:05       ` Deng, Pan
2023-06-28  5:18     ` Aaron Lu
2023-06-30  9:35       ` Aaron Lu [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=20230630093500.GA579792@ziqianlu-dell \
    --to=aaron.lu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lipeng.zhu@intel.com \
    --cc=pan.deng@intel.com \
    --cc=peterz@infradead.org \
    --cc=tianyou.li@intel.com \
    --cc=tim.c.chen@intel.com \
    --cc=tim.c.chen@linux.intel.com \
    --cc=vincent.guittot@linaro.org \
    --cc=yu.c.chen@intel.com \
    --cc=yu.ma@intel.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