From: Andi Kleen <andi@firstfloor.org>
To: "Kai" <epimetreus@fastmail.fm>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Serious performance regression in Wine applications and Linux 2.6.24.*
Date: 24 Mar 2008 04:55:36 +0100 [thread overview]
Message-ID: <87tziw7p3b.fsf@basil.nowhere.org> (raw)
In-Reply-To: <1206310206.17373.1243881033@webmail.messagingengine.com>
"Kai" <epimetreus@fastmail.fm> writes:
> Originally, it was just about everything -- Wine itself, and most any
> app I tried to run with it.
>
> In my most recent tests, however, it only seems to affect Age of Wonders
> II and Age of Wonders Shadow Magic, which use very similar engines.
A simple test if the scheduler is likely to blame would be to compare
context switch rates between the different kernel versions who show
differing performance. You can do that with running "vmstat 1" in
parallel and checking the "cs" column.
Another powerful but quite slow method if you can easily reproduce it
would be a full git bisect. That would identify exactly which change
introduced your problem.
-Andi
next prev parent reply other threads:[~2008-03-24 3:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-23 22:10 Serious performance regression in Wine applications and Linux 2.6.24.* Kai
2008-03-23 22:22 ` Ray Lee
2008-03-24 6:57 ` Kai
2008-03-27 9:17 ` Ingo Molnar
2008-04-03 14:04 ` Kai
[not found] ` <1207250856.9779.1245934881@webmail.messagingengine.com>
2008-04-21 15:53 ` Ingo Molnar
2008-04-22 2:58 ` Kai
2008-08-07 15:05 ` Kai
2008-03-24 3:55 ` Andi Kleen [this message]
2008-03-24 6:54 ` Kai
2008-03-24 7:09 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2008-03-23 2:49 Kai
2008-03-23 4:47 ` Ray Lee
2008-03-23 10:03 ` Kai
2008-03-25 12:12 ` Kai
2008-03-25 15:49 ` Ray Lee
[not found] ` <1207139425.16127.1245640599@webmail.messagingengine.com>
2008-04-02 12:40 ` Kai
2008-03-23 10:44 ` David
[not found] ` <1206309824.16550.1243881033@webmail.messagingengine.com>
2008-03-23 22:59 ` David
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=87tziw7p3b.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=epimetreus@fastmail.fm \
--cc=linux-kernel@vger.kernel.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