http://bugs.winehq.org/show_bug.cgi?id=22503
djamu djamu@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |UNCONFIRMED Resolution|INVALID |
--- Comment #4 from djamu djamu@hotmail.com 2010-04-27 07:41:35 --- (In reply to comment #3)
Closing invalid.
"wineserver is a separate application, and there is a context switch for every wineserver call. That's how it works."
I'm well aware of the function of wineserver. It's not a matter of context switches, it's a matter of rescheduling interupts. It doesn't happen when the memory load is under 1.8GB ( 8 threads ) > the average amount of rescheduling interupts is then 281/s.
There seems to be a treshold regarding a 2GB limit > then the rescheduling starts to spike to 2.29k/s ( I've observed situations with 10k/s rescheduling effectivily halting the proccess to a crawl )
I've thoroughly investigated the issue, do not reject this long term issue without testing. This issue exists in both wine32 wine64 so just answering wine64 is in alpha is not a valid answer I can supply you with all the programs to generate this kind of load, ( as there aren't that many ) > or just fire up the windows version of blender and render a scene >