Rajko M. wrote:
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)."
===
Right -- and to set priority "19", you use "nice -19 prog",
but you knew that, right? :-)
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.
---
No such thing in standard linux. The cpu nice doesn't affect
the disk-io priority unless you have the non-standard "cfq" scheduling
algorithm enabled. The default when I installed 10.2 recently, I believe
was the 'anticipatory' deadline. Unfortunately, while it may be good for
server workloads, and better for throughput, 'cfq' is better for
interactive use. A background process can easily saturate the disk if
it runs at full speed (even if process is 'niced' down).
In addition to using 'cfq' ('fair' queuing), you can run the
beagle processes in 'batch' priority -- which will be below normal user
processes.
Beagled -- is that a background indexer and beagle-helper is to
aid foreground searches? Or...why are there two processes?
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.
---
Mandb finishes after a few minutes - virtually never runs -- can't
see how it would drag down beagle... Course if it was a real beagle, just
wave some treats in front of it -- it'll get active & feisty! :-)
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.
---
If people think it is a problem, why not run it at 19? But a
disk-bound nice-19 process can still hog the system.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
