http://bugs.winehq.org/show_bug.cgi?id=28412
Summary: high processor usage of Reaper Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: gigaday@googlemail.com
I guess this isn't really a bug but I thought the feedback could be useful.
Reaper versions 3.xx and 4.xx with Wine 1.2.x and Wine 1.3.x use about 3 times as much processor power compared to MS Windows running Reaper on an equivalent processor.
With Reaper doing nothing processor usage is about 11% on Windows and about 36% with Wine on Ubuntu 11.04 when using a 2GHz processor.
http://bugs.winehq.org/show_bug.cgi?id=28412
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |performance Version|unspecified |1.2 Severity|normal |trivial
http://bugs.winehq.org/show_bug.cgi?id=28412
jbh@alchemy.lu changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jbh@alchemy.lu
--- Comment #1 from jbh@alchemy.lu 2012-01-19 02:38:34 CST --- There is an option prefs->audio->buffering->use native events for syncronizing. Turning it off makes reaper run a lot better. The drawback is still a lot of cpu usage due to using polling loops to syncronize the audio threads, but this problem mainly concerns reaper when idling. When actually doing audio processing the cpu power will become available to the audio thread.
My theory is that the wineserver architecture presents a bottle neck when using native events in this manner..
It helps to reduce the number of audio threads used when not needed, also in the buffering settings.
http://bugs.winehq.org/show_bug.cgi?id=28412
--- Comment #2 from Tony Austin gigaday@googlemail.com 2012-01-19 12:49:14 CST --- Thanks for the info. This and other tips can be found at:-
http://wiki.cockos.com/wiki/index.php/How_to_run_Reaper_in_Wine_on_Linux
https://bugs.winehq.org/show_bug.cgi?id=28412
--- Comment #3 from Austin English austinenglish@gmail.com --- This is your friendly reminder that there has been no bug activity for 2 years. Is this still an issue in current (1.7.16 or newer) wine?
https://bugs.winehq.org/show_bug.cgi?id=28412
--- Comment #4 from jbh@alchemy.lu --- AFAIK, it can safely be closed. The issue in the bug does no longer exist. There is no higher cpu use when enabling Native Events (I assume that some fast path was implemented), there is however a drawback in doing so, as sometimes the audio threads will have to wait on an event due to congestion in the wineserver, and you will get an audio under run that you won't get with the parameter disabled.
Reaper does use a lot of cpu to draw the gui, but that is unrelated to this bug and will hopefully go away some day :)
https://bugs.winehq.org/show_bug.cgi?id=28412
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED
--- Comment #5 from Austin English austinenglish@gmail.com --- (In reply to jbh from comment #4)
AFAIK, it can safely be closed. The issue in the bug does no longer exist. There is no higher cpu use when enabling Native Events (I assume that some fast path was implemented), there is however a drawback in doing so, as sometimes the audio threads will have to wait on an event due to congestion in the wineserver, and you will get an audio under run that you won't get with the parameter disabled.
Reaper does use a lot of cpu to draw the gui, but that is unrelated to this bug and will hopefully go away some day :)
Fixed.
https://bugs.winehq.org/show_bug.cgi?id=28412
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #6 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 1.7.26.
-
wine-bugs＠winehq.org