| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 7
|
|
| Author |
|
|
cjslman
Master Cruncher Mexico Joined: Nov 23, 2004 Post Count: 2082 Status: Offline Project Badges:
|
I'm currently running BOINC 6.10.58. Everything seems to be running OK (at least I haven't had anything blowup yet). Are there any compelling reasons that I should upgrade to 6.12? If there's nothing earth shattering, then I guess I'll wait until BOINC 7 is officially released into the wild.
----------------------------------------Thanks, CJSL ---------------------------------------- [Edit 1 times, last edit by cjslman at Jan 6, 2012 12:51:53 PM] |
||
|
|
Dark Angel
Veteran Cruncher Australia Joined: Nov 11, 2005 Post Count: 728 Status: Offline Project Badges:
|
I'm running 6.10.58 and have no trouble with it. I tried running the latest release but the manager program was flakey on my system. I don't know if it was unstable or just needed certain libs that I don't have or have the wrong version of. Regardless, this version works fine so there's no need to mess with it.
----------------------------------------![]() Currently being moderated under false pretences |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
To paraphrase a tech (offline) "there's nothing v.v. WCG that makes it compelling to upgrade from 6.10.58". Only those that do multi-grid computing *and* do GPU crunching have a better experience, because the GPU scheduling has had a lot of work done. Those exclusively dedicated to WCG would not benefit, as when opting in to do GPU at WCG would give 100% to WCG's 6.10.58 as is the word and will be able to deal with both NVidia and ATI/AMD GPU's. (platform specific compiles).
----------------------------------------Golly, yet another post that puts a thread off on the GPU track ;D --//-- P.S. Et al, "I've got the latest" or "tried the latest" type statements are not appreciated in the support department... we've no idea what is ''the latest''. Stating the version makes it clear if dealing with a buggy or ultra buggy release. [Edit 2 times, last edit by Former Member at Jan 6, 2012 10:04:00 AM] |
||
|
|
pcwr
Ace Cruncher England Joined: Sep 17, 2005 Post Count: 10903 Status: Offline Project Badges:
|
As the saying goes, "if it aint broke dont fix it".
----------------------------------------I run 6.2.28 on my P4 pc with no problems. I did upgrade to a newer version, but my P4 prefered the older version, so went back to that. I'm not sure what version my Win7 PCs are running (I'll have to check). Patrick ![]() |
||
|
|
Dark Angel
Veteran Cruncher Australia Joined: Nov 11, 2005 Post Count: 728 Status: Offline Project Badges:
|
P.S. Et al, "I've got the latest" or "tried the latest" type statements are not appreciated in the support department... we've no idea what is ''the latest''. Stating the version makes it clear if dealing with a buggy or ultra buggy release. Fair enough. My personal experience with 6.12.34 was less than stellar, but only regarding the manager. The client itself seemed fine. I'm not comfortable blaming the release outright since my OS build is rather custom, but something doesn't mesh between me and it that I haven't worked out yet. 6.10.58 on the other hand is rock solid for me. I don't normally play with beta releases and just about never play with alpha releases since I lack the patience to be a good tester. ![]() Currently being moderated under false pretences |
||
|
|
cjslman
Master Cruncher Mexico Joined: Nov 23, 2004 Post Count: 2082 Status: Offline Project Badges:
|
Gang.... thanks for all the responses. I got my answer. I'll stick with 6.10.58, which is working great for me (no need to go to 6.12). When release 7 is let loose, I'll see what goodies it has and decide if I should upgrade.
----------------------------------------Thanks, CJSL |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Yes, but long as only WCG is run, things are usually fine. Mind you, just came back from 13 days absence and switching on the 6.12.33 fitted Linux server/cruncher and only trickles of work were given... one at a time seeing cores idle for longer. Supposedly connect/crunch vars depreciation is halted if a client is off for longer than 10 days [IIRC], but now 2 days on, the cache has only build up to 6 on top of 4 crunching, when it's set to have 1.25 days worth per core. Testing 7.07 alpha on new lappY [octo threaded, details not shared here] and it took 10 days before set buffer was reached... not exactly a version for mobile crunchers who think to go pack their luggage for a week... you'd have to change settings days ahead to get enough stocked to crunch in half time.
--//-- |
||
|
|
|