ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@amacapital.net>
To: Chris Mason <clm@fb.com>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [TOPIC] Application performance: regressions, controlling preemption
Date: Mon, 12 May 2014 09:18:43 -0700	[thread overview]
Message-ID: <CALCETrXzKwnYaA1+UBG_Lr_b8XkSbGpXz0QBCR3fLGdH66hSBw@mail.gmail.com> (raw)
In-Reply-To: <5370DB7B.2040706@fb.com>

On Mon, May 12, 2014 at 7:32 AM, Chris Mason <clm@fb.com> wrote:
> Hi everyone,
>
> We're in the middle of upgrading the tiers here from older kernels (2.6.38,
> 3.2) into 3.10 and higher.
>
> I've been doing this upgrade game for a number of years now, with different
> business cards taped to my forehead and with different target workloads.
>
> The result is always the same...if I'm really lucky the system isn't slower,
> but usually I'm left with a steaming pile of 10-30% regressions.
>
> The KS dates should put us right at the end of our regression hunt, I can
> talk through the main problems we hit, how (if) we fixed them and hopefully
> offer tests to keep them from coming back.
>
> We've split the tiers up between Josef Bacik, Jens Axboe, myself and a few
> others.  I'd nominate Josef and Jens to come share their findings as well.
>
> Another topic here is controlling preemption from userland without needing
> to go full real time.  CPU intensive in-memory databases are leaving a ton
> of performance on the floor in context switches.  I'm hoping to experiment
> with better preemption controls and the userland RCU project to improve
> things.

I wonder how much of this overhead is the actual interrupt + context
switch and how much is overhead due to caching effects.  If the
former, there may be value in having a simple benchmark for how long
preemption takes and running it periodically.

--Andy

  parent reply	other threads:[~2014-05-12 16:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-12 14:32 Chris Mason
2014-05-12 15:05 ` Davidlohr Bueso
2014-05-12 15:57 ` Jan Kara
2014-05-12 16:18 ` Andy Lutomirski [this message]
2014-05-12 23:16 ` Greg KH
2014-05-13  1:43   ` Chris Mason
2014-05-14  1:31     ` Li Zefan
2014-05-14 12:27       ` Chris Mason
2014-05-13 12:27   ` Jan Kara
2014-05-12 23:54 ` Josh Triplett
2014-05-13  0:31   ` Davidlohr Bueso
2014-08-14 15:01     ` Fengguang Wu
2014-08-14 17:17       ` Christoph Lameter
2014-08-15  4:13         ` Fengguang Wu
2014-08-15 14:07           ` Christoph Lameter
2014-08-16  1:32             ` [Ksummit-discuss] 0day kernel performance/power test service Fengguang Wu
2014-05-28 17:08   ` [Ksummit-discuss] [TOPIC] Application performance: regressions, controlling preemption Paul E. McKenney
2014-08-18  6:21 ` Fengguang Wu

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=CALCETrXzKwnYaA1+UBG_Lr_b8XkSbGpXz0QBCR3fLGdH66hSBw@mail.gmail.com \
    --to=luto@amacapital.net \
    --cc=clm@fb.com \
    --cc=ksummit-discuss@lists.linuxfoundation.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