Skip to contentSkip to conversation

Serious performance regression in Wine applications and Linux 2.6.24.*

DISCUSSION Kai 3 participants 8 messages Mar 23, 2008 – Apr 2, 2008 2 messages not in the archive

lore
Share & tools
lore

Kai

author
#0 lore raw

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.

Please CC replies; I'm not on the list.

#1 lore raw
Quoted 11 lines · Kai

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).

author
#2 lore raw
Quoted 16 lines · Ray Lee
Quoted 11 lines · Kai

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.

Quoted 7 lines

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).

If anything, 2.6.25-rc6-git7 is even worse. Previously I've simply had delayed input, this time I had to actually kill the process, because it was unresponsive to keyboard input.

Here's the config file; I'm pretty sure I set it up correctly, (I just copied it from .24), but if I need to try it with any differing settings, let me know.

author
#3 lore raw
In reply to Ray Lee
Quoted 16 lines · Ray Lee
Quoted 11 lines · Kai

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.

Quoted 7 lines

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.

#4 lore raw
Quoted 26 lines · Kai
Quoted 21 lines · Ray Lee
Quoted 11 lines · Kai

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.)

Quoted 8 lines
Quoted 2 lines

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.

Andi's idea of looking for excessive context switches is good -- I didn't see a response to that one. Other than that, if you're only noticing the issue in 3d games, then it could be several things (not just the scheduler). Even just a few bisects (or testings of nightly snapshots) would help narrow it down.

Ray

A message that is not in the archive (sent off-list or not yet received): [email protected]

author
#6 lore raw
Quoted 36 lines · Ray Lee
Quoted 26 lines · Kai
Quoted 21 lines · Ray Lee
Quoted 11 lines · Kai

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.)

Quoted 8 lines
Quoted 2 lines

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.

Quoted 7 lines

Andi's idea of looking for excessive context switches is good -- I didn't see a response to that one. Other than that, if you're only noticing the issue in 3d games, then it could be several things (not just the scheduler). Even just a few bisects (or testings of nightly snapshots) would help narrow it down.

Ray

I'm going to do tests with his script right now; I'm moving, so testing is a bit delayed right now.
The game is actually 2D, not 3D, and sprite based. There is some (voxel?) based 3d combat, but the bug affects even the 2d map.

Preliminarily, I'm going to guess it's the CPU scheduler stuff, since I have noticed that any build which includes it also has the problem, but I can't say that definitively until I test a little more; I'll have more feedback soon.

Apologies for the delay,

-Kai

#7 lore raw
In reply to Kai
Quoted 9 lines · Kai

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.

Quoted 5 lines

I'd like some help figuring out why this performance regression exists, and what can be done to mitigate it.

Please CC replies; I'm not on the list.

This is strange, as my (two) Windows apps ran (and run) just fine under 2.6.24 (and now under 2.6.25-rc6). Could you specify the applications you're having problems with?

David

A message that is not in the archive (sent off-list or not yet received): [email protected]

#9 lore raw
Quoted 4 lines

This is strange, as my (two) Windows apps ran (and run) just fine under 2.6.24 (and now under 2.6.25-rc6). Could you specify the applications you're having problems with?

Quoted 9 lines · Kai

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.

On Sun, 23 Mar 2008 10:44:06 +0000, "David" <[email protected]> said:

OK.. I don't run Windows games, so won't have come across these issues. Hopefully someone with scheduler knowledge might be able to reproduce.

David