Gary, humbly apologize for being whiny/cranky about things and thanks ever so for taking the time to pen such an eloquent response. Yes my understanding about how things work is in fact growing; thanks to input/feedback from the community here. Thanks for bearing with me. Recent 50% task fails @Einstein prompted me to upgrade my video card which I installed yesterday and happily acquired a nice batch of work from SETI. I then Grabbed latest BOINC release, tuned my prefs in BAM and Einstein then Resumed it. Great to see my new hardware hummin along. Experimenting with Multi GPU configs ie my i5 onboard gfx capabilities (intent) and trying to troubleshoot effective drivers which is moot apparently but hadta *look and find out what I found out. Boils down to not understanding(yet)just what makes these apps happy and what I can do to enhance them on my end, if anything. I appreciate your BOINC notes and applaud the the amazing work shuffle perspective and goals. Truly, Kudos BOINC!
SETI down for maintenance all day apparently - just reported 11 tasks completed and BAM shifted work(60 minute timer) to Einstein + I turned up resources there to 100...crunchin away. Tempted to bump it to 200.
SETI already has 50+ tasks pending validation of mine, no doubt 30 more on that list I suspect - cant see it due to maintenance.
Anyhow Gary, thanks again. Humbly, Respectfully. JBird
PS @Gary, great advice re: adjusting my cache; please point me to where the cache settings are, I can't find them
Cache settings are in Computing preferences on Your Account page (at any project, they are a global preference, set at any project, apply to all), or locally in Boinc Manager in Tools>computing preferences>network usage.
But if you're using BAM, you should be able to set them there.
With Boinc 7, they in the form of a Minimum Buffer setting, and an Additional Buffer setting,
Boinc 7 originally would fillup to the Minimum plus Additional Buffer, then wait for the amount of work to fall to below the Minimum before asking for work again,
But later changes mean now Boinc 7 will now ask for work if it's reporting work, so there is less likelihood of a big gap between filling up with work, and getting your next batch,
additionally Boinc used to cache completed tasks upto 24 hours before reporting them, now it's one hour,
The minimum buffer setting also has the effect of telling Boinc how many days offline the host is going to have, meaning for every day added to the minimum buffer, Boinc will try to complete work an extra day earlier.
(This can be a problem with Seti users who use Big caches, they find they get Einstein work, or work from other projects with short deadlines,
then find Boinc will run their 2nd project in preference to Seti as their 2nd project is deadline trouble because of their high minimum buffer setting, and because Boinc has to the work x many days early too)
... shifted work(60 minute timer) to Einstein + I turned up resources there to 100...crunchin away. Tempted to bump it to 200.
Please resist the temptation :-). Think about it for a moment. If you keep changing resource shares, don't you think BOINC might get a little confused about your intentions? You are far better off deciding on a set of shares and then sticking to it so that BOINC can settle into a pattern. BOINC probably tends to work best if all projects have roughly equal shares. If one project is your favourite then give it a somewhat bigger share but then leave those settings alone until you really want to select a different favourite project.
Gary, humbly apologize for
)
Gary, humbly apologize for being whiny/cranky about things and thanks ever so for taking the time to pen such an eloquent response. Yes my understanding about how things work is in fact growing; thanks to input/feedback from the community here. Thanks for bearing with me. Recent 50% task fails @Einstein prompted me to upgrade my video card which I installed yesterday and happily acquired a nice batch of work from SETI. I then Grabbed latest BOINC release, tuned my prefs in BAM and Einstein then Resumed it. Great to see my new hardware hummin along. Experimenting with Multi GPU configs ie my i5 onboard gfx capabilities (intent) and trying to troubleshoot effective drivers which is moot apparently but hadta *look and find out what I found out. Boils down to not understanding(yet)just what makes these apps happy and what I can do to enhance them on my end, if anything. I appreciate your BOINC notes and applaud the the amazing work shuffle perspective and goals. Truly, Kudos BOINC!
SETI down for maintenance all day apparently - just reported 11 tasks completed and BAM shifted work(60 minute timer) to Einstein + I turned up resources there to 100...crunchin away. Tempted to bump it to 200.
SETI already has 50+ tasks pending validation of mine, no doubt 30 more on that list I suspect - cant see it due to maintenance.
Anyhow Gary, thanks again. Humbly, Respectfully. JBird
PS @Gary, great advice re:
)
PS @Gary, great advice re: adjusting my cache; please point me to where the cache settings are, I can't find them
RE: PS @Gary, great advice
)
Cache settings are in Computing preferences on Your Account page (at any project, they are a global preference, set at any project, apply to all), or locally in Boinc Manager in Tools>computing preferences>network usage.
But if you're using BAM, you should be able to set them there.
With Boinc 7, they in the form of a Minimum Buffer setting, and an Additional Buffer setting,
Boinc 7 originally would fillup to the Minimum plus Additional Buffer, then wait for the amount of work to fall to below the Minimum before asking for work again,
But later changes mean now Boinc 7 will now ask for work if it's reporting work, so there is less likelihood of a big gap between filling up with work, and getting your next batch,
additionally Boinc used to cache completed tasks upto 24 hours before reporting them, now it's one hour,
The minimum buffer setting also has the effect of telling Boinc how many days offline the host is going to have, meaning for every day added to the minimum buffer, Boinc will try to complete work an extra day earlier.
(This can be a problem with Seti users who use Big caches, they find they get Einstein work, or work from other projects with short deadlines,
then find Boinc will run their 2nd project in preference to Seti as their 2nd project is deadline trouble because of their high minimum buffer setting, and because Boinc has to the work x many days early too)
Claggy
RE: ... shifted work(60
)
Please resist the temptation :-). Think about it for a moment. If you keep changing resource shares, don't you think BOINC might get a little confused about your intentions? You are far better off deciding on a set of shares and then sticking to it so that BOINC can settle into a pattern. BOINC probably tends to work best if all projects have roughly equal shares. If one project is your favourite then give it a somewhat bigger share but then leave those settings alone until you really want to select a different favourite project.
Cheers,
Gary.