From: Artem Bityutskiy <dedekind1@gmail.com>
To: Rik van Riel <riel@redhat.com>
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org,
mgorman@suse.de, jhladky@redhat.com, mingo@kernel.org
Subject: Re: [PATCH RFC] numa,sched: have fbq_classify_* factor out the current task
Date: Thu, 21 May 2015 15:13:43 +0300 [thread overview]
Message-ID: <1432210423.2703.54.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <20150519105544.68caa726@annuminas.surriel.com>
On Tue, 2015-05-19 at 10:55 -0400, Rik van Riel wrote:
> The load balancer tries to find, through find_busiest_group and
> find_busiest_queue, a busy CPU with tasks that are running on
> the wrong NUMA node.
>
> However, the load balancer only moves runnable-but-not-running
> tasks in most situations. This fails horribly when the current
> task on a CPU is on the wrong NUMA node, but the other task(s)
> on the run queue are placed correctly.
>
> In that situation, what started out as one misplaced tasks
> quickly turns into two misplaced tasks.
>
> Try to avoid that by factoring out the placement of the current
> task, in order to find groups and runqueues with misplaced tasks
> that are not currently running.
>
> Signed-off-by: Rik van Riel <riel@redhat.com>
This seem to give small improvement for our eCommerce web workload,
average sever response time went down from ~1.4 to ~1.34. I can run the
workload for longer time to get better numbers.
Thanks,
Artem.
prev parent reply other threads:[~2015-05-21 12:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 14:55 Rik van Riel
2015-05-21 12:13 ` Artem Bityutskiy [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=1432210423.2703.54.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=jhladky@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=riel@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 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®