Gary Baribault wrote:
Hi all,
Anyone else seeing Beagle really kill performance? I have disabled
it and my machine finally is perky, but every now and then, I find it
in memory again. How do I arange it to chew up less memory and CPU or
kill it once and for all?
---
Might try making sure the "cfq" block algorithm is being used,
then set 'beagle' to run at lowest priority (nice -19 beagle-start-script).
That should help it not use so much CPU, and, if cfq is working
well, it should set beagle's disk priority to near lowest as well.
Of course, if beagle is using 500MB and you only have 512MB, you are
likely
to get "alot" of swapping.
I'd also wonder, does beagle use "alot" of resources during
some initial "full-index" phase, after which it can run with less resources
as it does incremental updates...?
BTW -- anyone compared it to "swish" (another full-system indexing util with
web-based interface).
Linda
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
