Carlo Cabanilla <[email protected]> writes: > Is there a good way of keeping awesome responsive even when certain > clients are using up all the cpu? Maybe something clever with cgroups?
Dear Carlo, usually Linux manages cpu usage quite well, preventing freezes by dynamically increasing priority for low cpu consuming processes (such as awesome wm). Which clients reduce responsiveness ? I suppose that responsiveness issues caused by some other reasons, for example by swapping, or by using slow widgets in awesome. Have you tried to disable all third party widgets in awesome ? -- To unsubscribe, send mail to [email protected].
