[Bug 45209] New: Staging 3.8 crippling preformance degradation
https://bugs.winehq.org/show_bug.cgi?id=45209 Bug ID: 45209 Summary: Staging 3.8 crippling preformance degradation Product: Wine Version: 3.8 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: themainliner(a)hotmail.com Distribution: --- Performance in several Blizzard games (Heroes of the Storm, World of Warcraft) significantly reduced after upgrading to winehq-staging 3.8. FPS in World of Warcraft, for example, never fluctuated from 2 fps redering both WoW and HotS unplayable. This is likely a duplicate of another as I expect this performance degradation is effecting many, if not all, games titles. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45209 tokktokk <fdsfgs(a)krutt.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fdsfgs(a)krutt.org -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45209 Ker noa <blue-t(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |blue-t(a)web.de --- Comment #1 from Ker noa <blue-t(a)web.de> --- Have you tried 3.8 wine without staging patches? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45209 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |leslie_alistair(a)hotmail.com --- Comment #2 from Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> --- Can you provide a +d3d11 log? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45209 Józef Kucia <joseph.kucia(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |-unknown CC| |erich.e.hoover(a)wine-staging | |.com, | |joseph.kucia(a)gmail.com, | |michael(a)fds-team.de, | |sebastian(a)fds-team.de Product|Wine |Wine-staging Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #3 from Józef Kucia <joseph.kucia(a)gmail.com> --- I guess that the regression is caused by https://github.com/wine-staging/wine-staging/blob/master/patches/d3d11-dynam... -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45209 --- Comment #4 from Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> --- (In reply to Józef Kucia from comment #3)
I guess that the regression is caused by https://github.com/wine-staging/wine-staging/blob/master/patches/d3d11- dynamic-cpu-access/0001-d3d11-D3D11_USAGE_DYNAMIC-needs-to-have-CPU-access. patch
Probably. Without this patch, I get a blank screen when running the 64bit version of this Diablo 3. With the patch I can get to the character screen, but have low FPS. The 32 bit version for works without fault with/out that patch. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45209 --- Comment #5 from Józef Kucia <joseph.kucia(a)gmail.com> --- (In reply to Alistair Leslie-Hughes from comment #4)
The 32 bit version for works without fault with/out that patch.
Does the 32-bit version use d3d11? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45209 --- Comment #6 from Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> --- (In reply to Józef Kucia from comment #5)
(In reply to Alistair Leslie-Hughes from comment #4)
The 32 bit version for works without fault with/out that patch.
Does the 32-bit version use d3d11?
No, it uses the dx9 interfaces. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45209 --- Comment #7 from Józef Kucia <joseph.kucia(a)gmail.com> --- (In reply to Alistair Leslie-Hughes from comment #6)
(In reply to Józef Kucia from comment #5)
(In reply to Alistair Leslie-Hughes from comment #4)
The 32 bit version for works without fault with/out that patch.
Does the 32-bit version use d3d11?
No, it uses the dx9 interfaces.
Ok. So, the 0001-d3d11-D3D11_USAGE_DYNAMIC-needs-to-have-CPU-access patch workarounds bug 45066 (which is likely Nvidia legacy driver bug), and it severely degrades performance in d3d11 apps on all drivers. FWIW, I think that buffer mapping optimizations for constant buffers might also "fix" bug 45066 in the future. It might be also better to use nouveau instead of legacy Nvidia drivers. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45209 --- Comment #8 from Ker noa <blue-t(a)web.de> --- nouveau on modern GPUs from NVIDIA maxwell/pascal has no reclocking, so the performance would be equally bad -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45209 --- Comment #9 from Józef Kucia <joseph.kucia(a)gmail.com> --- (In reply to Ker noa from comment #8)
nouveau on modern GPUs from NVIDIA maxwell/pascal has no reclocking, so the performance would be equally bad
The patch should be removed from staging. The comment about nouveau was regarding bug 45066. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45209 alasky(a)codeweavers.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alasky(a)codeweavers.com -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45209 --- Comment #10 from Ker noa <blue-t(a)web.de> --- (In reply to Alistair Leslie-Hughes from comment #2)
Can you provide a +d3d11 log?
how can you pipe all wine output to a file ? Im struggling with WINEDEBUG=+d3d11 wine64 Wow-64.exe --launch 2>&1 >> test.out and also trying to saving terminal output alone gives me mostly empty lines -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45209 --- Comment #11 from Ker noa <blue-t(a)web.de> --- Created attachment 61451 --> https://bugs.winehq.org/attachment.cgi?id=61451 3.8 staging trace for d3d11 Right now with 1-3fps, hope it helps -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45209 Kevin Brott <winebugz(a)kbrm.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |winebugz(a)kbrm.net -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45209 --- Comment #12 from Ker noa <blue-t(a)web.de> --- 3.9 staging dropped the patch in question. So i think we can safely close this bug -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45209 themainliner <themainliner(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #13 from themainliner <themainliner(a)hotmail.com> --- Resolved in staging 3.9 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45209 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #14 from Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> --- Closing Fixed Staging 3.14 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org