On 6/29/05, Anders Johansson
On Tuesday 28 June 2005 22:07, Adam Vazquez Kb2Jpd wrote:
There is also that find and slocate routine that starts up after your machine is idling. It is busy finding all the text and making a search index. control alt f1 logon root and killall slocate and killall find when you need to.
If updatedb is seriously affecting your performance (especially on a modern 64 bit machine) then you have a DMA configuration problem. I would suggest you make sure you have it enabled on your hard drives
I'm not using Konq much (Firefox as a browser). I sometimes have it open in filemanager mode... but not that often. I don't see slocate running, and updatedb also doesn't seem to be the culprit - if it is, it's running every 30 seconds... which it's not. DMA.... as far as I know all SATA drives use DMA by default. I also don't see anything when I look at the cronjobs. I get the CPU spikes even if Oracle is shut down and killed. I'll have to keep hunting I guess... frustrating though since I find that my new AMD64 3000+ work computer is slower than my old 2.2GHz Celeron at home (both running SuSE9.3). :-( C.