On Wednesday 19 December 2007 04:54:01 am Linda Walsh wrote:
Rajko M. wrote: ...
--- 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? :-)
I knew what info tells: nice -n <niceness> program In practice it accepts also nice -19 program and nice --19 program for negative values. It is just the way you quoted command line that confused me. It appeared to me as text. ....
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?
You question is the answer :-) http://beagle-project.org/Main_Page I can't see Joe Shaw, jumping in discussion. He knows the best about the beagle.
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...
It was 2 processes competing about single hard disk and few minutes computer was in very bad shape, and it was computer that had no problems with quite a few applications running at the same time. I experienced the problem and initially I was against Beagle, but Joe helped to find real reason for problems and ever since I can't see it as a resource hog. I'm just happy user.
Course if it was a real beagle, just wave some treats in front of it -- it'll get active & feisty! :-)
Sure :-)
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.
Yes, but this is not the case with Beagle here. The problem was solved in 10.2, and should not appear in 10.3, unless Mono jumped in as regression factor. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org