| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: BOINC: v7 Minimum work buffer / Max additional work buffer & v6 Connect about every xx days / Additional work buffer operation |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 40
|
|
| Author |
|
|
Dataman
Ace Cruncher Joined: Nov 16, 2004 Post Count: 4865 Status: Offline Project Badges: 
|
I have not put a 7.0.x version up on the test machine yet. So I think I will do that today. I'm on 64-bit and wondering why the 32-bit version is 7.95 meg and the 64-bit version 9.25 meg. Seems like a large difference. I plan to run it on the machine that runs CPDN/GPUGrid. Anything to look out for?  Unless you really need it such as for POEM or Albert OpenCL applications, I would steer clear myself. Wouldn't touch it with a barge pole. In my experience the changed work buffer policies do not work well for GPU projects that have limited/intermittent availability of work and there may be other bugs as sometimes found in development versions. If you set a high Minimum work buffer with return results immediately in order to get POEM tasks, you then need to manually update your CPU projects every day after resetting the buffers lower. Otherwise you will end up with inconsiderately large caches on quorum CPU projects. It's only once a day so not really a trouble but with the release versions this extra fiddling is not necessary. If POEM had better work availability, I would rather just run 2 instances of Windows BOINC using a release BOINC version for CPU projects or use my VirtualBox Linux BOINC for CPU projects. However I prefer to use freed up CPU cores for CPU projects if POEM GPU runs out of work. Does GPUGrid still have a bonus for early return of tasks? If so and you need to set a higher Minimum work buffer for any reason you may need to use return results immediately or an AutoUpdate script on GPUGrid or perhaps miss out on the bonus. Thanks again. I have GPUGrid set to accept only 6.15 Long Runs (approx 36,000 credits/wu) and they run approx 7-10 hours on a 400 series card. I'm not sure about the others. Skgiven would know as he runs a lot there.   |
||
|
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges: 
|
DM. Shoot me an e-mail when you get the chance. I have some questions. Thanks.
----------------------------------------
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
BOINC: Connect Every xx Days and Additional Buffer use. Comments more than questions. From a reader's perspective, I found the use of CE and AB in connection with 7.xx confusing, given that those functions have been renamed. As the FAQ has one paragraph about 6.xx behaviour and 3 paragraphs and a screenshot about 7.xx, the FAQ title is similarly confusing or at best incomplete.-- Draft FAQ: As the actual Preferences wording (in 6.10.58) is "Connect about every" and "Additional work buffer", it would be good to have those in the title to facilitate searches. Maybe the title should be Use of "Connect about every", "Additional work buffer" / "Minimum work buffer", "Max additional work buffer". I suggest you retain CE and AB for the 6.xx paragraph, but change fully to some abbreviations for "Minimum work buffer" and "Max additional work buffer" for the 7.xx paragraphs (the first of which can still mention the renaming) - e.g. MinBuf and MaxAddBuf. The 6.xx paragraph should also define CE as the abbreviation for Connect (about) every, similarly to how you do it for AB (and ditto the 7.xx abbreviations where they're first introduced). Thanks for putting the effort in creating this FAQ and all the others; I've used them many times! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thanks for the comments, but it was until 6.12 clear as a bell what CE and AB stood for and how they worked, one adding to the other, the reason why the old way gets little verbiage, not needing a specific FAQ until now and the new way allot more... for those who don't use barge poles and will upgrade when the "A New Version is available. Download It" starts showing in their 5.xx, 6.xx clients.
Draft being draft, I'll incorporate some of your suggestions, whilst avoiding to overextend the item and find that same switch off at the 3rd paragraph, as is the case here demonstrated when the questions still came about needing to upgrade when it said in the addendum "As of last word, WCG is not going to need an upgrade to run their upcoming GPU project!"  --//-- |
||
|
|
Richard Mitnick
Veteran Cruncher USA Joined: Feb 28, 2007 Post Count: 583 Status: Offline Project Badges: 
|
I do not see that BOINC has released a 7.X version yet.
---------------------------------------- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Quoting myself:
... when the "A New Version is available. Download It" starts showing in their 5.xx, 6.xx clients. --//-- |
||
|
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges:
|
----------------------------------------
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
You're referring to a project that requires specific releases, still very much in development as it says at top "About CERNVM/Vboxwrapper Test Project". Those enrolled over there would get messages through notices, not originating in Berkeley. As I understand it, this project is going to get binned when testing is done.
------------------------------------------//-- [Edit 1 times, last edit by Former Member at Feb 6, 2012 7:00:54 PM] |
||
|
|
Richard Mitnick
Veteran Cruncher USA Joined: Feb 28, 2007 Post Count: 583 Status: Offline Project Badges:
|
nanoprobe-
----------------------------------------Yes, sure, and I am actually a participant there; but I don't know why this "project" would be a part of any discussion. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
In case it escaped, I edited into an earlier post that 7.0.12-7.0.14 alpha are thoroughly unfit for running at WCG. They mangle .gzb files [seeing odd posts on our forums suggesting more are walking into this wall].
Internal note by tech says though that where 7 is going with transmitted file compression handling is what they've wanted for a long time, but it has to be backward compatible of course. Maybe this leads to better download/upload rate measurement by BOINC too? Away from the aside, the main being that once used to thinking minimum / maximum [cache], it's almost like "why did the developers not do this long ago ;?". --//-- |
||
|
|
|