[Bug 28412] New: high processor usage of Reaper
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(a)winehq.org ReportedBy: gigaday(a)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. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=28412 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |performance Version|unspecified |1.2 Severity|normal |trivial -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=28412 jbh(a)alchemy.lu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jbh(a)alchemy.lu --- Comment #1 from jbh(a)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. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=28412 --- Comment #2 from Tony Austin <gigaday(a)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 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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=28412 --- Comment #3 from Austin English <austinenglish(a)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? -- 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=28412 --- Comment #4 from jbh(a)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 :) -- 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=28412 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Austin English <austinenglish(a)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. -- 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=28412 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #6 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 1.7.26. -- 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