Also, artsd has gone back to eating 10-17% of the CPU for the 60 second 'autosusped if idle for' period after a sound event. After the 60 second autosuspend period, artsd quiets back down. Why are we setting a 60 second autosuspend by default? Why not set it to 1 or 5 seconds. It would sure make TDE run better giving users back 10-20% of their CPU for the remaining 55 seconds of the timeout. Further, if the user has sound events enabled for a bulk of the events as many sound themes do for TDE, then with an autosuspend set at 60, artsd will be basically grinding away full time.
Can we set that to 5 sec by default instead of 60? What are the pros/cons of shortening the autosuspend period? I've seen some of the sound server pages (pulse - perfect setup page) recommending 1 second for the setting. Thoughts?
I have that set to 2 seconds on all of my systems, including my PI and PII clunkers.
Yes, 60 seconds seems absurd.
Darrell
On 02/02/2014 04:45 PM, Darrell Anderson wrote:
I have that set to 2 seconds on all of my systems, including my PI and PII clunkers.
Yes, 60 seconds seems absurd.
Darrell
For some reason selecting sound system notifications did not take effect until TDE was restarted -- I have never seen that happen before. If that is permanent, we should add a dialog stating that a TDE restart is required like with font anti-aliasing...