You will notice that seti@home runs at normal application priority(4).
It also uses a large amount of memory for it's processing.
I have not noticed any problems with it not releasing memory, was it set up to run
constantly?
That would definitely cause problems, unless you have an incredibly overpowered
system -- i.e.. you never hit 100% usage without seti@home or prime95, etc.
It would be best on systems that are otherwise not used most of the time and have
plenty of memory.
It would be nice if they offered an option to set the priority, but running it
while doing other things would cause a lot of swap file usage unless you have
extra memory.
Kevin Sexton
37% done with 5315483 after nearly finishing on v.17
________________________________________________________________
Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm
