From: Jan Kara <jack@suse.cz>
To: Greg KH <greg@kroah.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TOPIC] Application performance: regressions, controlling preemption
Date: Tue, 13 May 2014 14:27:24 +0200 [thread overview]
Message-ID: <20140513122724.GB22070@quack.suse.cz> (raw)
In-Reply-To: <20140512231648.GA17027@kroah.com>
On Tue 13-05-14 01:16:48, Greg KH wrote:
> On Mon, May 12, 2014 at 10:32:27AM -0400, Chris Mason 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.
>
> How long have we been having this discussion? 8 years? It's not like
> people don't know that performance testing needs to be constantly
> happening, we've been saying that for a long time. It's just that no
> one seems to listen to us :(
I agree with you that this is coming over and over again for quite a few
years.
> And that is the larger problem, what can we do about that issue.
> Honestly, I don't think much, as it takes money from companies to commit
> to do this work, which no one seems to ever want to do. What make this
> year the year that something different happens?
So what I found interesting about the topic is:
1) What has regressed this time in particular? This might be interesting
for a broader audience I believe. With my SUSE hat on, I can learn which
problems should I expect our customers to see that we didn't find during
our testing. With my community hat on, I can possibly learn some things
which are easy enough to test for...
2) We are looking into some more continuous testing in SUSE so learning
what others have tested would be interesting for me.
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2014-05-13 12:27 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
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 [this message]
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=20140513122724.GB22070@quack.suse.cz \
--to=jack@suse.cz \
--cc=greg@kroah.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