Ok, heres the deal...i detatched and (re)attatched seti@home to the BOINC client yesterday and once it started, it only downloaded a few WU's. the time for completion was set to 22hrs for each WU, when actually its just under 3.5hrs. I guess thats why it downlaods only a few WUs, enough to last me the given days @22hrs/WU...but after completing and uploading 2WU's (both crunched at 3.4hrs) it still d/ls 2 WU;s and says 'Time to completion 22:51'!
What can i do to solve this problem?
----------------------------
Join Team X-Beyond The Frontier!

Make your catche bigger, do it for something like 20-21 days, but you can also try closing all apps and do a bench mark, might help it :).

The time "To Completion" is CPU time and not wall clock time. If a lot of processes are running or not, this will not change at all the time "To Completion" as well as the "CPU time".
Benchmarking has no influence also on the time to complete processing of a WU. It has only an influence on the amount of claimed credit.
I would recommend increasing the cache size only gradually and keeping an eye on the CPU time that is needed for finishing analyzing one WU. If the cache is set too high, it can happen that the processing of a WU starts once the "Report Deadline" time is already past.


Greetings from Belgium.

> Make your catche bigger, do it for something like 20-21 days, but you can also
> try closing all apps and do a bench mark, might help it :).

Yikes! This is not good advice. This will virtually ensure that you get way more work than you can complete before they expire. Large cache numbers like this are not to be trifled with, even as an experiment.

<a> [/url]

I have the same problem...I'm pretty sure that my p4 2.8HT will not need the 29 hours the program is counting on...more like 3/4 hours..so my cache is down to like 8 wu's, which will probably become a problem if the servers/splitters whatever they're working on go offline....

> I have the same problem...I'm pretty sure that my p4 2.8HT will not need the
> 29 hours the program is counting on...more like 3/4 hours..so my cache is down
> to like 8 wu's, which will probably become a problem if the servers/splitters
> whatever they're working on go offline....
>

I had opposite problem. My "Time to completion" predistion was 27 min, but reality is 3h 20min. I got too many WUs.
But after I finished and sent a couple of WUs and downloaded new ones, "To completion" time changed to 3:17. It seems there is some approximation process. So wait a while, I hope your "Time to completion" will come close to reality.

Spok

> > I have the same problem...I'm pretty sure that my p4 2.8HT will not need
> the
> > 29 hours the program is counting on...more like 3/4 hours..so my cache is
> down
> > to like 8 wu's, which will probably become a problem if the
> servers/splitters
> > whatever they're working on go offline....
> >
>
> I had opposite problem. My "Time to completion" predistion was 27 min, but
> reality is 3h 20min. I got too many WUs.
> But after I finished and sent a couple of WUs and downloaded new ones, "To
> completion" time changed to 3:17. It seems there is some approximation
> process. So wait a while, I hope your "Time to completion" will come close to
> reality.
>
> Spok
>

i hope so too! just completed a few WU's, and uploading them now. i'll see what happens. i used to get a proper time before, but after detatching the project and reattatching it, i got this problem. but since then ive uploaded only 1-2 WU's. now that i got a few more done, i'll let u guys know what happens.
----------------------------
Join Team X-Beyond The Frontier!

ok...still dont work. Apparantly everyones been having the same problem so i guess its at Berkleys end. hopefully the issue will be resolved soon
----------------------------
Join Team X-Beyond The Frontier!