Jan Allan Andersen wrote:

Martin 53N 1W wrote:

Better is to run boinc from a script or as a service. "Howto"s for
these have been posted on the s@h boinc forum.

Must have a closer look at that :o)

All the boinc clients save checkpoints so that if they are
interrupted, they can roll back to a recently saved point. Leaving
the processes in memory saves wasting CPU time that would otherwise
be lost by rolling back. CP especially should be kept in memory!

I also have that, but again, if I have to close down my linux
completely, will the WU's kept in memory be completely lost then?
Or will a script help that?

At the moment for s@h, quite a bit faster if you believe the screams
from the Windows users. I suspect that some OS interaction is causing
problems. The s@h developers are looking into whether the problems
are real and what to fix.

I asked because it is my experience also, especially in regards to
SETI2. I have BOINC installed on my windows partition too, and it
takes something like 6� - 7, and more likely around 7, hours to
complete a WU. In linux, installed on a slower HD, it takes around 4�
hour to complete.

Regards,
Jan

yeah i'm seeing that currently
i have a single p3 1ghz on windows, it takes 13.7 hours a wu or so (win2000)
dualy p3 1ghz is taking 9.6 hours a work unit, linux 2.4 kernel

they do kinda need to fix that
my own pc is doing em at about 3:20 3:30, winxp currently