Hi All, I've posted for some suggestions in the WoW forums, but it's been suggested that I post here as well, as I'm more likely to get someone who has a clue :) PROBLEM ===== After an extended play time in one area (~ 1 hour), or rapid travel between areas, the performance degrades substantially. It goes from 60+ FPS to about 5FPS and doesn't recover until I restart the game. A restart brings an instant performance boost, even in the same area I just logged out. For instance, I was just in Icecrown (up in the air, looking at a large landscape), getting 5fps. I logged out and in, and am now getting 45fps. This seems to indicate it's not a graphics performance issue (ie. I don't have quality settings set too high). It's not just the low framerate either, it's constantly stop-starting which basically adds up to making it near impossible to play. HARDWARE/CONFIG ============CPU - AMD Phenom(tm) 9950 Quad-Core Processor (@2.6GHz) Memory: 4GB Video Card: GeForce 9800 GT Card OS: Fedora 10 Wine Version: 1.1.14 (Fedora package) OTHER NOTES ========I've noted that memory usage is sensible. Prior to writing this post, I just restarted a game which only had a resident size of 980mb. The OS had plenty of free memory. I've adjusted just about every setting or tweak in the game to try and isolate the issue, including different timing mode settings which can be tweaked. Nothing has succeeded in resolving the issue. The problem has persisted through multiple Wine versions, and seems to get no better or worse. Thanks in advance for any help :)
Can't say I really have any issues like this. I did however notice some kind of memory leak introduced in a recent version of wine or WoW. Over say 4 hours, the WoW process eats up to about 1GB of RAM. That just continues with longer gameplay. Even still, I don't experience any performance degredation. I'd be suggesting checking the obvious... does glxgears performance suffer too when WoW performance suffers? If it does, it's your graphics card or associated drivers. Perhaps the fan's duty cycle is too low leading to gradually higher temps? How about CPU usage? Mine is constantly at about 100% usage of one core (got 3). Does it decrease or increase for you?
Well under.. like tops out at 75-80 degrees.
I seem to be having somewhat similar issues lately. Unfortunately I haven't been able to pin down the problem yet as lots of things changed. I went from 64 bit Kubuntu 8.-something, older NV drivers, wow 3.0.3 to 64bit Gentoo with 180.-something NV drivers, latest Wine and wow patch 3.0.9. Before the change I only had somewhat lowish performance on some of the bossfights but was rockstable. After the change the game crashes almost randomly, gets graphical glitches every now and then (usually soon followed by crash), is awfully slow on nearly every bossfight and over time eats up 2GB of my 6G RAM. It shouldn't be the addons as I'm using the exact same ones I used before, I haven't even updated them.> > >-- Kalle Last -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.winehq.org/pipermail/wine-users/attachments/20090312/c13af3cc/attachment.htm>
Seems the very simple (one line) change has fixed the performance issues I was having, however it's also created a new one... crash after about 2 hours. I'm going to try recompiling with one of the other patches (there's one which has a huge chunk of files) and see how I go.
This problem isn't limited to WoW, I get the exact same symptoms described here (abrupt performance degradation, restart resets everything) in Civilization IV and Red Alert 2. With Civilization it happens after only about 10 minutes of play, while Red Alert 2 can run for over an hour. If it's an issue with Nvidia drivers, a large range of them are affected as I'm using the 169 series OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce 6800 GT/PCI/SSE2/3DNOW! OpenGL version string: 2.1.2 NVIDIA 169.12
>This problem isn't limited to WoW, I get the exact same symptoms described here (abrupt performance degradation, restart resets everything) in Civilization IV and Red Alert 2. With Civilization it happens after only about 10 minutes of play, while Red Alert 2 can run for over an hour. > >If it's an issue with Nvidia drivers, a large range of them are affected as I'm using the 169 series > >OpenGL vendor string: NVIDIA Corporation >OpenGL renderer string: GeForce 6800 GT/PCI/SSE2/3DNOW! >OpenGL version string: 2.1.2 NVIDIA 169.12I'm wondering if the same problem makes Dragon NaturallySpeaking 10 Standard crash after exactly 12 minutes.
Looks like this patch fixes the problem: http://bugs.winehq.org/attachment.cgi?id=19905 The trick is, you need to use the mem=4G option as well, otherwise your games (or at least WoW) will launch but be invisible.
Rico <wineforum-user at winehq.org> wrote on March 27th:> >loltsy wrote: >> Looking at the virtual size of the process it starts around 2600M where with a 64bit system it started around 3600M. After flying around all over the world and running some instances it seems to float around the 3G mark. Well short of the 4G crash that takes about 30 seconds to get to on 64bit. > > >I tried that, too, with this result: > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND >l32 w32: 5793 ich 20 0 2598m 8556 6524 S 0.0 0.3 0:00.16 notepad >l32pae w32: 5760 ich 20 0 2598m 8564 6536 S 0.0 0.1 0:00.21 notepad >l64 w32: 4445 Ricola 20 0 3622m 9040 6544 S 0.0 0.1 0:00.13 notepad > >This table shows the output of top after "rm -rf ~/.wine && wine notepad" on linux 32Bit, 32Bit+pae, 64Bit. The main difference is the VIRT memory. Why is it ~1GB higher on 64Bit systems than on 32Bit systems? >The results are quite interesting. It is possible there is unoptimized code in Wine 64 bit. The question I have is this immediately after running the program or after a set time period, say ten minutes? If it is immediately, then my statement is basically correct and work needs to be done to optimize code for 64 bit. If it is after ten minutes, then there is a leak somewhere that is causing this and it should be investigated. James McKenzie
James Mckenzie wrote:> The question I have is this immediately after running the program or after a set time period, say ten minutes? If it is immediately, then my statement is basically correct and work needs to be done to optimize code for 64 bit. If it is after ten minutes, then there is a leak somewhere that is causing this and it should be investigated.This is immediately after the start (<1 min). Also I tried the wine 32bit version ("w32") on all 3 systems (it was exactly the same build). It doesn't look like memory leak, because the numbers were constant over this time. But I could run it a little bit longer.