I have been running boinc now since it was released in its current state.
first boinc expected to have my work units done in 5 hours which is pretty correct as it really takes 4 hours.
but the last few days boinc suddenly thinks it will take about 30 hours, why is this???
have not changed anything.
the annoying part is that my cue is now very small and with the servers being more down then up my cpu is most of the time doing nothing
i dont want to change the amount of days work that are downloaded because if boinc were to calculate the correct time again for some weird reason i could end up with much to many work units that i cannot handle
so if anyone could help me fix this problem i would be a happy man again.
I have a P4 2.8GHz 1024 MB ram

Ok I already got some useful answers but know i would like to know if it would not be handy to let boinc remember the average completion time of say the last 50 finished work units.
This would give a nice representation of the time needed to complete a work unit.
And of course I also thought about the people just starting boinc. boinc should be programmed so that when you start processing your first unit the completion time estimate should be set to 10 hours or so.
then when you finish work units the completion time will be slowly averaged towards your real completion times and after 50 units it will be on your real average.
please let me know what you other people think of this idea
maybe it is brilliant maybe I am crazy

I don't think this is a problem. Let it run...
Normaly on one of my machines I get WU's which complete in 11 tot 13 hours.
I happened to receive workunits which finished in 2 to 5 minutes on the same computer.
Yesterday I even did receive a WU, for which Seti gave as expected time 101 hours!!! Astonishing...
But this has been mentioned before on this website (don't know the exact place anymore). The idea was it had to do with a lot of statics and disturbances during the recording of the tape at the radiotelescope in Arecibo.
I think that the program will sort this out. So my advice let it run as long as it doesn't get stuck.

Greetings ;-))

You will find in the "Message boards" under "Crunching" this message that gives an explanation on it.

You might also use the search function.


Greetings from Belgium.

> I don't think this is a problem. Let it run...
> Normaly on one of my machines I get WU's which complete in 11 tot 13 hours.
> I happened to receive workunits which finished in 2 to 5 minutes on the same
> computer.
> Yesterday I even did receive a WU, for which Seti gave as expected time 101
> hours!!! Astonishing...
> But this has been mentioned before on this website (don't know the exact place
> anymore). The idea was it had to do with a lot of statics and disturbances
> during the recording of the tape at the radiotelescope in Arecibo.
> I think that the program will sort this out. So my advice let it run as long
> as it doesn't get stuck.
>
> Greetings ;-))
>
>
> <img> src="http://seti.mundayweb.com/stats.php?userID=92&trans=off">
>
>
>

Ok thanks
ofcourse i will let it run
would not dare dream of turning seti of :-)