| Author |
Message |
|---|
|
|
|
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?
-----------------
<a>Join Team X-Beyond The Frontier![/url]
 |
|
|
|
|
|
> 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?
> -----------------
The estimated time for completion is off, nothing you can do about it. I hope that this is fixed soon.
|
|
|
|
|
|
> The estimated time for completion is off, nothing you can do about it. I hope
> that this is fixed soon.
I am using a HT P4 running at 2.88GHz. The time for processing was until now between 3:10:39 and 4:35:40. The freshly downloaded WU's have a completion time of 31:09:58. The first one will start processing in roughly 5 hours from now.
I will see tomorrow morning what will be the final processing time.
Greetings from Belgium. |
|
|
|
|
|
Yeah, it doesn't look too accurate. My 1.4 Pentium M notebook does a WU in 2:15 - 2:30, but the "to completion" time displayed is 5:06 per WU.
I guess the trick is to set one's preferences to cache a few more WU's than necessary, since the computer number Boinc Seti will send is lower than it should be (based on the actual crunching times verses benchmark calculations.) |
|
|
|
|
|
> The estimated time for completion is off, nothing you can do about it. I hope
> that this is fixed soon.
I have the same situation. Boinc on one PC (the others are ok) downloaded 7 which it marked as 21 hours for completion.
Incidently John, where did you get this info from?
 |
|
|
|
|
|
> Yeah, it doesn't look too accurate. My 1.4 Pentium M notebook does a WU in
> 2:15 - 2:30, but the "to completion" time displayed is 5:06 per WU.
>
> I guess the trick is to set one's preferences to cache a few more WU's than
> necessary, since the computer number Boinc Seti will send is lower than it
> should be (based on the actual crunching times verses benchmark calculations.)
>
The problem with this advice is that when the error is fixed you will suddenly have huge amounts of extra work. The team will get this fixed sooner or later just wait it out.
John Keck
BOINCing since 2002/12/08 |
|
|
|
|
|
> > Yeah, it doesn't look too accurate. My 1.4 Pentium M notebook does a WU
> in
> > 2:15 - 2:30, but the "to completion" time displayed is 5:06 per WU.
> >
> > I guess the trick is to set one's preferences to cache a few more WU's
> than
> > necessary, since the computer number Boinc Seti will send is lower than
> it
> > should be (based on the actual crunching times verses benchmark
> calculations.)
> >
> The problem with this advice is that when the error is fixed you will suddenly
> have huge amounts of extra work. The team will get this fixed sooner or later
> just wait it out.
>
John Keck
> BOINCing since 2002/12/08
>
 |
|
|
|
|
|
John,
Well, the problem with waiting for it to be fixed is I'm going to be away from two of my computers for around 10 days. I have to use dial-up so I need the work units before I leave and can't wait for a "maybe fixed".
|
|
|
|
|
|
> John,
>
> Well, the problem with waiting for it to be fixed is I'm going to be away from
> two of my computers for around 10 days. I have to use dial-up so I need the
> work units before I leave and can't wait for a "maybe fixed".
> |
|
|
