On Sunday 16 December 2007 04:19:48 pm Linda Walsh wrote: > 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).
info:nice "Nicenesses range at least from -20 (resulting in the most favorable scheduling) through 19 (the least favorable)." > 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 Beagle is actually silent helper in background. There was problem in initial release of 10.2 where it was started Beagle and mandb. Running both on same hard disk made system sluggish, and that happened on every boot, few minutes after GUI was up. Many users noticed Beagle and missed to see mandb, and since removing one of programs that were competing for hard disk access made situation much better, Beagle earned bad reputation and it is still comming back trough Google search. Beagle-helper runs now with nice=19, so it is already the lowest priority and it will not make problem even on initial indexing. The beagled runs with nice=7, so it is also below most processes in the system. -- Regards, Rajko -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
