On Wed, 10 Dec 2008 05:26:02 +0000
Patrick Kilgore <email address hidden> wrote:
> From what it sounds like, these programs are just going temporarily
> unresponsive due to high system load. This happens on every operating
> system and usually all it requires is a short wait before the system
> can catch up to all the recent input/data manipulation. There is an
> option to disable the window "gray" effect in compiz if you do not
> like it, although its purpose is to remind you to wait a second and
> allow the computer to "catch up" so to speak. The more demanding the
> program, the more you tend to see this happen.
on further examination it is not a matter of system load. memory use
is not spiking and cpu utilisation is not high either. often the cpu
is not even scaling up when the freezes occur.
On Wed, 10 Dec 2008 05:26:02 +0000
Patrick Kilgore <email address hidden> wrote:
> From what it sounds like, these programs are just going temporarily
> unresponsive due to high system load. This happens on every operating
> system and usually all it requires is a short wait before the system
> can catch up to all the recent input/data manipulation. There is an
> option to disable the window "gray" effect in compiz if you do not
> like it, although its purpose is to remind you to wait a second and
> allow the computer to "catch up" so to speak. The more demanding the
> program, the more you tend to see this happen.
on further examination it is not a matter of system load. memory use
is not spiking and cpu utilisation is not high either. often the cpu
is not even scaling up when the freezes occur.
Bran