[Bug 40490] New: Poor Drakensang Online performance in wine version over 1.9.5 (tested in 1.9.6 and 1.9.7)
https://bugs.winehq.org/show_bug.cgi?id=40490
Bug ID: 40490 Summary: Poor Drakensang Online performance in wine version over 1.9.5 (tested in 1.9.6 and 1.9.7) Product: Wine Version: 1.9.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: bartek@failpoint.pl Distribution: ---
There was always (maybe since wine 1.2, I don't remember) this poor game performance in Drakensang Online while using wine. But in wine-1.9.5 the performance was very good. After upgrade to 1.9.6/1.9.7 game performance is poor again. What I discovered is that my APU temperature is the same as in idle when playing game using 1.9.6/1.9.7 but is getting hot (normal behavior) when playing game using 1.9.5. Also top shows that CPU utilization is below 140% in wine 1.9.6/7 and over 230% in wine 1.9.5. So it looks like in 1.9.6/7 it is in some economic mode or sth.
https://bugs.winehq.org/show_bug.cgi?id=40490
--- Comment #1 from Matteo Bruni matteo.mystral@gmail.com --- You're probably testing wine-staging, right? I think in version 1.9.6 CSMT was disabled which would explain the performance degradation, the lower CPU usage and the cooler APU temperature.
https://bugs.winehq.org/show_bug.cgi?id=40490
--- Comment #2 from bk76 bartek@failpoint.pl --- I'm using Gentoo and I have staging flag set so I think that it is wine-staging but I don't know what it is. So what should I do, disable staging and test 1.9.6 and 1.9.7 again?
https://bugs.winehq.org/show_bug.cgi?id=40490
--- Comment #3 from bk76 bartek@failpoint.pl --- Ok, I checked my wine and it is wine-stageing. I disabled CSMT in winecfg and result is the same as when using wine 1.9.6 and 1.9.7.
https://bugs.winehq.org/show_bug.cgi?id=40490
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID CC| |sebastian@fds-team.de
--- Comment #4 from Sebastian Lackner sebastian@fds-team.de --- (In reply to bk76 from comment #3)
Ok, I checked my wine and it is wine-stageing. I disabled CSMT in winecfg and result is the same as when using wine 1.9.6 and 1.9.7.
Wine Staging 1.9.6+ does no longer ship CSMT because the old patchset is no longer compatible. Developers are currently working on the integration of this feature into the development branch, and as part of that, a lot of parts have to be cleaned up and also be rewritten from scratch.
Your answer sounds like you are basically comparing performance with and without CSMT, which makes the bug report invalid. If you need those performance improvements before the feature is upstream or has been reenabled, it is recommended to stick to Wine Staging 1.9.5.
https://bugs.winehq.org/show_bug.cgi?id=40490
--- Comment #5 from Henri Verbeet hverbeet@gmail.com --- (In reply to Sebastian Lackner from comment #4)
Wine Staging 1.9.6+ does no longer ship CSMT because the old patchset is no longer compatible. Developers are currently working on the integration of this feature into the development branch, and as part of that, a lot of parts have to be cleaned up and also be rewritten from scratch.
The number of developers working on integrating CSMT is a bit more limited than that statement sees to imply. I think it's also fair to point out that this is exactly the reason why the CSMT patch set wasn't integrated into Wine in its original form, and more generally why publishing a tree with patches you're not capable of/willing to maintain yourself is a bad idea.
https://bugs.winehq.org/show_bug.cgi?id=40490
--- Comment #6 from Sebastian Lackner sebastian@fds-team.de --- (In reply to Henri Verbeet from comment #5)
The number of developers working on integrating CSMT is a bit more limited than that statement sees to imply. I think it's also fair to point out that this is exactly the reason why the CSMT patch set wasn't integrated into Wine in its original form, and more generally why publishing a tree with patches you're not capable of/willing to maintain yourself is a bad idea.
I am aware that some users might be disappointed by the decision to remove the patchset again, but I am confident that the majority will understand the concept of Wine Staging a bit better. Disabling patches if they are no longer worth the effort to maintain is nothing unusual, and part of the concept. As you can see, users were pretty happy to try out those features in the meantime.
https://bugs.winehq.org/show_bug.cgi?id=40490
--- Comment #7 from bk76 bartek@failpoint.pl --- (In reply to Henri Verbeet from comment #5)
(In reply to Sebastian Lackner from comment #4)
Wine Staging 1.9.6+ does no longer ship CSMT because the old patchset is no longer compatible. Developers are currently working on the integration of this feature into the development branch, and as part of that, a lot of parts have to be cleaned up and also be rewritten from scratch.
The number of developers working on integrating CSMT is a bit more limited than that statement sees to imply. I think it's also fair to point out that this is exactly the reason why the CSMT patch set wasn't integrated into Wine in its original form, and more generally why publishing a tree with patches you're not capable of/willing to maintain yourself is a bad idea.
Yes, I know that now. CSMT is what I need and I will just stick to wine-1.9.5 until CSMT reach upstream.
https://bugs.winehq.org/show_bug.cgi?id=40490
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #8 from Bruno Jesus 00cpxxx@gmail.com --- Closing invalid bugs.
-
wine-bugs＠winehq.org