From: Li Zefan <lizefan@huawei.com>
To: Chris Mason <clm@fb.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TOPIC] Application performance: regressions, controlling preemption
Date: Wed, 14 May 2014 09:31:37 +0800 [thread overview]
Message-ID: <5372C779.8070602@huawei.com> (raw)
In-Reply-To: <537178CA.60303@fb.com>
On 2014/5/13 9:43, Chris Mason wrote:
> On 05/12/2014 07:16 PM, 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 :(
>>
>
> Yes and no. Intel listened, and I think they have had a huge positive
> impact here. Others have as well, maybe not as consistently, but still.
>
> I do find it really interesting that even with huge improvements all
> over the place, we have a very hard time upgrading production workloads
> without hitting big regressions.
>
> Sometimes it is just a few .config entries,
Do you mean some regressions are introduced by new configs i.e. new
features? If so, I don't think that can be strictly called regressions.
> and sometimes we paper over
> it with improvements in other areas, but it's almost always worse.
>
next prev parent reply other threads:[~2014-05-14 1:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 14:32 [Ksummit-discuss] [TOPIC] Application performance: regressions, controlling preemption 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 [this message]
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=5372C779.8070602@huawei.com \
--to=lizefan@huawei.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.