E@H Cache vs Deadline
27 Jan 2005 3:04:34 UTC
Topic 187370
(moderation:
Have 3 E@H work units cached and 4 S@H wu's. E@H units all due 30 Jan 05. S@H wu's due 6 Feb 05 or 9 Feb 05. PII 400 takes ~65 hours/wu for E@H, ~16 hrs/wu for S@H. Resources split 50/50 between E@H and S@H. E@H cache doesn't seem to be allowing enough time to complete units before deadline. Have more E@H wu's cached than remaining time allotted without running S@H. Boinc 4.19, E@H 4.73, S@H 4.02 kernel 2.6.8, Mandrake 10.1.
E@H Cache vs Deadline
)
How large is your cache set? Sounds like you might want to scale it back...
www.clintcollins.org - spouting off at the speed of site
Go to 1 day or less, for
)
Go to 1 day or less, for connect time and change your Resource to 25% Seti@H and 75% E@H.
Or go to 1 project or upgrade your system........
Link to Unofficial Wiki for BOINC, by Paul and Friends
See this
)
See this thread.
http://einsteinathome.org/node/187369
Team MacNN - The best Macintosh team ever.
Thanks for the link. Had S@H
)
Thanks for the link. Had S@H set to 5 days since it used to go down for long periods. Just set up E@H the same way initially. Have changed cache to 2 days. Still I'm surprised the project caches don't "communicate" in some way to prevent too large a overall cache.
I have my cache setting at
)
I have my cache setting at 1.5 days and that seems to give me enough work for 4-5 days so I have enough time to finish the WU's the Server gives me. When I first joined the project I had it set to 5 days & that was way to high for a 7 day deadline limit I found out so I backed off my settings ...
Since the master boinc client
)
Since the master boinc client has benchmark data and presumably access to cached wu sizes and predicted process times it seems like it should have a housekeeping function to limit overall cache size to fit the deadline(s). Otherwise, you may have wu's that get discarded or not processed that have to be recycled, wasting crunching time. Note to admin, has this idea been considered :)
I agree. The Einstein
)
I agree. The Einstein scheduler/BOINC CC apparently do NOT take resource share into account when calculating how much work is required to satisfy the cache that is set.
On one of my machines (running all five public projects, with E@H getting twice the resources of the others, I had three WUs on the machine, all with a projected run time of 10:45, all with a deadline later this afternoon (two obviousely would not meet that deadline), and a cache of three days. There is NO WAY that all three of these will be done with three days, but BOINC just requested an additional 2628 seconds of work!
> Thanks for the link. Had
)
> Thanks for the link. Had S@H set to 5 days since it used to go down for long
> periods. Just set up E@H the same way initially. Have changed cache to 2
> days. Still I'm surprised the project caches don't "communicate" in some way
> to prevent too large a overall cache.
>
You have a misconception. The General settings affect all projects. You do not get to set a different cach3e size per project.
BOINC WIKI
The BOINC scheduler does not
)
The BOINC scheduler does not take deadlines into account when deciding which WUs to crunch, or even whether to download more WUs. I have been attempting to bring this to the attention of the BOINC developers for quite a while.
BOINC WIKI
> The BOINC scheduler does
)
> The BOINC scheduler does not take deadlines into account when deciding which
> WUs to crunch, or even whether to download more WUs. I have been attempting
> to bring this to the attention of the BOINC developers for quite a while.
>
There are task list items for this, just noone has gotten around to doing anything with it. I am not sure if the fact that BOINC wants a full queue for each project is directly listed in any of them though.
One thing that slipped by when they made max queue length settings is that if you set your queue at a project with a higher max it will not get lowered if you are also attached to a project with a lower max.
BOINC WIKI
BOINCing since 2002/12/8