From: "Kai" <epimetreus@fastmail.fm>
To: "Ray Lee" <ray-lk@madrabbit.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Serious performance regression in Wine applications and Linux 2.6.24.*
Date: Tue, 25 Mar 2008 05:12:02 -0700 [thread overview]
Message-ID: <1206447122.8428.1244147147@webmail.messagingengine.com> (raw)
In-Reply-To: <2c0942db0803222147y27954bd6hf4cb0cc98ceda2da@mail.gmail.com>
On Sat, 22 Mar 2008 21:47:52 -0700, "Ray Lee" <ray-lk@madrabbit.org>
said:
> On Sat, Mar 22, 2008 at 7:49 PM, Kai <epimetreus@fastmail.fm> wrote:
> > Performance degrades by about 60% when I run Wine under any of the
> > 2.6.24.* kernels. Attached are the output of lspci -vv and the two
> > config files of each kernel.
> >
> > I upgraded to 2.6.24, back to 2.6.23.(not sure), then tried 2.6.24.1 and
> > 2.6.24.3 and the issue is present in both; it's severe enough that Wine
> > apps are virtually unusable for me with this version of the kernel; I'm
> > having to use 2.6.23 until this somehow is resolved.
> >
> > I'd like some help figuring out why this performance regression exists,
> > and what can be done to mitigate it.
>
> As wine has a 'wineserver' running in a separate process, it may be
> related to scheduler changes.
>
> Regardless, if you have the time, please retest using he latest git
> head (or nightly snapshot), and see if the performance regression is
> still there, and report back. (There have been a lot of changes
> between 2.6.24 and current git head that impact the scheduler.)
>
> Please ensure that the fair group scheduler is disabled in your tests
> (just as you have in your 2.6.24 config you attached).
As mentioned in another response, it was happening as recently as
2.6.25-rc6-git7; I'm currently performing a git bisect between 2.6.23
and 2.6.24, unless someone has a better idea; it seems my best option,
as I'm not really very experienced with kernel hacking or debugging.
next prev parent reply other threads:[~2008-03-25 12:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-23 2:49 Serious performance regression in Wine applications and Linux 2.6.24.* Kai
2008-03-23 4:47 ` Ray Lee
2008-03-23 10:03 ` Kai
2008-03-25 12:12 ` Kai [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2008-03-23 22:10 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
2008-03-24 6:54 ` Kai
2008-03-24 7:09 ` Andi Kleen
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=1206447122.8428.1244147147@webmail.messagingengine.com \
--to=epimetreus@fastmail.fm \
--cc=linux-kernel@vger.kernel.org \
--cc=ray-lk@madrabbit.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.