Re: The State of GNOME (Matthias Warkus) writes:

> > Another classic example is gtop. A simple utility, you might think.
> > Allows me to check out the CPU usage of the processes running on my
> > machine. Yet when I fire up gtop, it sucks up 11% of my CPU. There's
> > no such thing as immature code to destroy performance.
> In case you haven't yet noticed: it's not unusual for even a normal
> console top(1) running at an update every 0.5 seconds to eat 10%-20%
> CPU, too.

You can use the properties dialog to lower update intervals. Performance
things are also an issue for LibGTop 1.1.0.

Martin Baulig - -

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]