From: Parth Shah <parth@linux.ibm.com>
To: Vincent Guittot <vincent.guittot@linaro.org>,
mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
dietmar.eggemann@arm.com, rostedt@goodmis.org,
bsegall@google.com, mgorman@suse.de,
linux-kernel@vger.kernel.org
Cc: pauld@redhat.com, valentin.schneider@arm.com, hdanton@sina.com
Subject: Re: [PATCH v4 0/5] remove runnable_load_avg and improve group_classify
Date: Sun, 23 Feb 2020 11:38:23 +0530 [thread overview]
Message-ID: <a095f3ef-10d8-b58b-4d84-ac4b06fd91d1@linux.ibm.com> (raw)
In-Reply-To: <20200221132715.20648-1-vincent.guittot@linaro.org>
Hi,
On 2/21/20 6:57 PM, Vincent Guittot wrote:
> This new version stays quite close to the previous one and should
> replace without problems the previous one that part of Mel's patchset:
> https://lkml.org/lkml/2020/2/14/156
>
> NUMA load balancing is the last remaining piece of code that uses the
> runnable_load_avg of PELT to balance tasks between nodes. The normal
> load_balance has replaced it by a better description of the current state
> of the group of cpus. The same policy can be applied to the numa
> balancing.
>
> Once unused, runnable_load_avg can be replaced by a simpler runnable_avg
> signal that tracks the waiting time of tasks on rq. Currently, the state
> of a group of CPUs is defined thanks to the number of running task and the
> level of utilization of rq. But the utilization can be temporarly low
> after the migration of a task whereas the rq is still overloaded with
> tasks. In such case where tasks were competing for the rq, the
> runnable_avg will stay high after the migration.
>
> Some hackbench results:
>
> - small arm64 dual quad cores system
> hackbench -l (2560/#grp) -g #grp
>
> grp tip/sched/core +patchset improvement
> 1 1,327(+/-10,06 %) 1,247(+/-5,45 %) 5,97 %
> 4 1,250(+/- 2,55 %) 1,207(+/-2,12 %) 3,42 %
> 8 1,189(+/- 1,47 %) 1,179(+/-1,93 %) 0,90 %
> 16 1,221(+/- 3,25 %) 1,219(+/-2,44 %) 0,16 %
>
> - large arm64 2 nodes / 224 cores system
> hackbench -l (256000/#grp) -g #grp
>
> grp tip/sched/core +patchset improvement
> 1 14,197(+/- 2,73 %) 13,917(+/- 2,19 %) 1,98 %
> 4 6,817(+/- 1,27 %) 6,523(+/-11,96 %) 4,31 %
> 16 2,930(+/- 1,07 %) 2,911(+/- 1,08 %) 0,66 %
> 32 2,735(+/- 1,71 %) 2,725(+/- 1,53 %) 0,37 %
> 64 2,702(+/- 0,32 %) 2,717(+/- 1,07 %) -0,53 %
> 128 3,533(+/-14,66 %) 3,123(+/-12,47 %) 11,59 %
> 256 3,918(+/-19,93 %) 3,390(+/- 5,93 %) 13,47 %
[...]
I performed similar experiment on IBM POWER9 system with 2 nodes 44 cores
system (22 per node)
- hackbench -l (256000/#grp) -g #grp
+-----+----------------+-------+
| grp | tip/sched/core | v4 |
+-----+----------------+-------+
| 1 | 76.97 | 76.31 |
| 4 | 56.56 | 56.86 |
| 8 | 54.23 | 54.25 |
| 16 | 53.94 | 53.24 |
| 32 | 54.10 | 54.01 |
| 64 | 54.38 | 54.35 |
| 128 | 55.11 | 55.08 |
| 256 | 55.97 | 56.04 |
| 512 | 54.81 | 55.5 |
+-----+----------------+-------+
- deviation in the result is very marginal ( < 1%)
The results shows no changes with respect to the hackbench. I will do
further benchmarking to see if any observable changes occurs.
- Parth
next prev parent reply other threads:[~2020-02-23 6:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 13:27 Vincent Guittot
2020-02-21 13:27 ` [PATCH v4 1/5] sched/fair: Reorder enqueue/dequeue_task_fair path Vincent Guittot
2020-02-21 13:27 ` [PATCH v4 2/5] sched/numa: Replace runnable_load_avg by load_avg Vincent Guittot
2020-02-23 6:32 ` Parth Shah
2020-02-21 13:27 ` [PATCH v4 3/5] sched/pelt: Remove unused runnable load average Vincent Guittot
2020-02-21 13:27 ` [PATCH v4 4/5] sched/pelt: Add a new runnable average signal Vincent Guittot
2020-02-24 10:05 ` Parth Shah
2020-02-21 13:27 ` [PATCH v4 5/5] sched/fair: Take into account runnable_avg to classify group Vincent Guittot
2020-02-21 15:09 ` [PATCH v4 0/5] remove runnable_load_avg and improve group_classify Mel Gorman
2020-02-23 6:08 ` Parth Shah [this message]
[not found] ` <20200222055522.9548-1-hdanton@sina.com>
2020-02-24 8:32 ` [PATCH v4 5/5] sched/fair: Take into account runnable_avg to classify group Vincent Guittot
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=a095f3ef-10d8-b58b-4d84-ac4b06fd91d1@linux.ibm.com \
--to=parth@linux.ibm.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=hdanton@sina.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=pauld@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=valentin.schneider@arm.com \
--cc=vincent.guittot@linaro.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
all inboxes | Powered by JetHome®