"Time to completion" set way too high

Questions and Answers : Preferences : "Time to completion" set way too high
Message board moderation

To post messages, you must log in.

AuthorMessage
The Postman
Avatar

Send message
Joined: 4 Jan 03
Posts: 78
Credit: 14,960,413
RAC: 74
United States
Message 8034 - Posted: 14 Jul 2004, 21:36:48 UTC

How can I reduce this figure to a reasonable number. For my P4 it is set at 48 hours and for my P2 it is 113 hours. With numbers like these, I have to set my cache to 30 days just to get 3-4 days ahead. These machines run 24/7.
ID: 8034 · Report as offensive
Profile Jaaku
Volunteer tester
Avatar

Send message
Joined: 29 Oct 02
Posts: 494
Credit: 346,224
RAC: 0
United Kingdom
Message 8037 - Posted: 14 Jul 2004, 21:51:59 UTC

yea, i think seti have added a debug in there it make the wu look longer.
ID: 8037 · Report as offensive
Profile KWSN - MajorKong
Volunteer tester
Avatar

Send message
Joined: 5 Jan 00
Posts: 2892
Credit: 1,499,890
RAC: 0
United States
Message 8053 - Posted: 14 Jul 2004, 22:27:01 UTC

> How can I reduce this figure to a reasonable number.

You don't. If I remember correctly, someone was trying to balance the estimated time on one of the platforms, and goofed. Not much you can do about it, except to continue to crunch through the affected work units until they are gone (not every work unit is affected).

> For my P4 it is set at 48 hours and for my P2 it is 113 hours.

Yes, I see similar times as well (28 hours on my XP1800, > 100 hours on my P2).

> With numbers like these, I have to set my cache to 30 days just
> to get 3-4 days ahead. These machines run 24/7.

Please don't set your cache that high. Seti@home work units 'last' only 14 days until they expire, and the scheduler won't (shouldn't) give you anything it thinks you can't finish in time.

In my opinion, if, as Jaaku implies, Berkeley is using this 'oops' to help ration out scarce work units, you should not be trying to 'get greedy' anyway. Just leave your cache at the value you mentioned (3 to 4 days), and accept the 'dry times'. If you, and a large number of other people, keep trying to 'game the system' into giving them a larger amount of work than it wishes, the 'dry times' are lengthened for everyone, and Berk will have a lot harder time trying to build up a decent surplus of work. If you 'game' the scheduler into giving you 6x the number of work units it would normally give you, thats 5 other people you have screwed into sitting dry.

So, please don't run up you cache preferences to some rediculous amount. Please just leave your cache preferences at some normal value (the figure you mentioned of 3 to 4 days is good, in my opinion), and be patient on Berkeley to work things out.
ID: 8053 · Report as offensive
Profile Thierry Van Driessche
Volunteer tester
Avatar

Send message
Joined: 20 Aug 02
Posts: 3083
Credit: 150,096
RAC: 0
Belgium
Message 8055 - Posted: 14 Jul 2004, 22:31:59 UTC
Last modified: 20 Jul 2004, 12:08:57 UTC

As mentionned in another thread:

The work estimates are being reverted back to their launch day estimates today, we should start to see them show up in the workunit pool very soon.

----- Rom
BOINC Development Team, U.C. Berkeley
.




Greetings from Belgium.
ID: 8055 · Report as offensive

Questions and Answers : Preferences : "Time to completion" set way too high


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.