http://bugs.winehq.org/show_bug.cgi?id=22503
Summary: wineserver: massive amount of rescheduling interupts / context switches on +1.8GB application load ( both wine32 / wine64 ) Product: Wine Version: 1.1.43 Platform: All OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: wineserver AssignedTo: wine-bugs@winehq.org ReportedBy: djamu@hotmail.com
Created an attachment (id=27570) --> (http://bugs.winehq.org/attachment.cgi?id=27570) memory usage vs CPU load from 2.1GB to 1.7GB RAM
Wineserver creates a massive amount of rescheduling interupts / context switching when using + 1.8GB RAM application load, both on Wine32 and the Wine64 versions ( meaning the 64 bit Wine, not the 32 bit for 64bit systems ) The rescheduling becomes very apparant when going over 2GB RAM usage, and will effectively hog down an SMP processor to a crawl.
For a long time I've been using Wine to succesfully run various brands of renderers ( Lightwave / Maya / Fryrender / Maxwell ... )
The problem exists already for a long time, but became very apparant when I recently switched (compiled) to Wine64 because of a big project. ( Previous projects never needed the amount of ram needed for the current one )
Reverting back to Wine32 bit ( which should run fine as long as I stay under 4GB ) showed me the exact same slow down, except that on wine32 "top" for some reason doesn't show visually wineserver consuming a lot of resources ( only visible on Wine64 ) ... nevertheless the amount of rescheduling interupts and context switches skyrocket at exact the same loads for both versions.
This behaviour is visible on various ( CLI based ) multithreaded renderers which makes me confident in believing it is not related to a renderer specific DLL.
I would flag this bug as major as in quite a short while other applications / games will encounter the same issue.
I know a fair share of programming and can do some debugging, but I'm not very familiar with all the Wine components / not sure what logs / graphs I should submit ( I've got quite a few ). Any debug commands to pinpoint the problem are usefull too.
The added graph shows the CPU load/interupts whith variable memory usage from +2.1GB to +1.7GB on a compute node > the lower the memory usage, the higher the CPU load. ( ignore the halted state between 8.30PM/5AM )
Thx
Jan Van Haute