Firebird -> Firefox

[Roger Oberholtzer]

The only KDE resource hog is memory. Or, to be more precise, KDE does not
seem to steal CPU time when you are not actively doing anything in KDE. We
have lookd at this closely as we have a demanding app that requires swift
response time and uses lots of CPU time. When running KDE this requirement
is met.

With two exceptions:

1. (And this is probably generally X and not KDE itself) When moving the
mouse on the display so that it moves from window to window (i. e., to
process to process), you can add a couple of thousand process switches per
second to the system load. Depends on the number of windows around and how
fast you move the mouse. A lack of memory requires that at least part of
the app is swapped in to handle the possible mouse activity. Leading to
generally slow response time all around. (Play with ksysguard to see this
yourself.) Mice are not cheap.

2. artsd very often eats CPU time when no apparent sound or other audio
activity is happening. This seems to still be a bad part of KDE. I have
played with letting it or not letting it have real time priority, but that
seems to have no effect. I have seen discussions about this all over the
place. None end in a resolution of the problem.

So, given memory, KDE is not so very bad. 256M is ok, but on the limit.




-- 
+????????????????????????????+???????????????????????????????+
? Roger Oberholtzer          ?   E-mail: roger at opq.se        ?
? OPQ Systems AB             ?      WWW: http://www.opq.se/  ?
? Erik Dahlbergsgatan 41-43  ?    Phone: Int + 46 8   314223 ?
? 115 34 Stockholm           ?   Mobile: Int + 46 733 621657 ?
? Sweden                     ?      Fax: Int + 46 8   302602 ?
+????????????????????????????+???????????????????????????????+