| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Beta Testing
Forum: Beta Test Support Forum
Thread: Settings that might make me miss out on Betas? |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 15
|
|
| Author |
|
|
OldChap
Veteran Cruncher UK Joined: Jun 5, 2009 Post Count: 978 Status: Offline Project Badges: 
|
Gentlemen, thank you all for your comments.
----------------------------------------I'm not sure why but when searching through the faq's I totally missed the information I needed. Your comments referring to them confirmed their existence so eventually it was a matter of trawling through with screen magnification turned up and.... voilà. Profile changes made to "switch between apps" time otherwise, for now, I have left well enough alone.  [Edit 1 times, last edit by OldChap at Jan 19, 2012 11:37:15 PM] |
||
|
|
Mathilde2006
Senior Cruncher Germany Joined: Sep 30, 2006 Post Count: 269 Status: Offline Project Badges:
|
Please check out the link in your signature- it's:
----------------------------------------http://"http//www.xtremesystems.org/forums/forumdisplay.php?f=207 ^^^^^^^^ This can't work. ;-)  |
||
|
|
Ingleside
Veteran Cruncher Norway Joined: Nov 19, 2005 Post Count: 974 Status: Offline Project Badges: 
|
Yes, but that is for work the client ''has'', not for what it wants to receive, anhhai. As long as the client is not in an alert / hi priority state of processing on all cores/threads, work will be fetched of any deadline denomination! So the proposition of not getting beta on a high cache will still get the Russian answer. Beta FAQ, last paragraph, first line. (Why do we write them?) Getting beta-work or not with a "large" cache should depend on how you're setting the cache. If "Connected..." > 4 days and beta-work has a deadline of 4 days, the scheduling-server should not send you any beta-work, since client has no chance to return it by the deadline if client is really so long offline as user has indicated. In practise most users with a large "Connected..." will connect more frequently than specified so there wouldn't be any problems to send beta-work, but scheduling-server can't know this so must use the "worse-case"-scenario of client being offline for > 4 days... Now, things is made more difficult since even scheduling-server should not send any work with shorter deadline than "Connected..." but this is over-ruled in case doesn't have enough work in project to keep all cpu's busy. But appart for the very few instances there someone is out of enough WCG-work to keep all cores busy, they'll not get beta-work with 4-days deadline if their "Connected..." > 4 days.  "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Except for using the "Connect Every" [who does?], the thing being, it does, Ingleside, case you're not getting the message. Here's where the next client's behavior is going to stump many, but that's not what we're discussing... it's the here and now clients in production. Most run "additional buffer / cache setting with a low connect interval and when using 7 the present dev version is not going to send much at all [the hysteresis discussion if you're following] ;>)
--//-- |
||
|
|
OldChap
Veteran Cruncher UK Joined: Jun 5, 2009 Post Count: 978 Status: Offline Project Badges:
|
Please check out the link in your signature- it's: http://"http//www.xtremesystems.org/forums/forumdisplay.php?f=207 ^^^^^^^^ This can't work. ;-) Done. Thanks, I forgot about the different format here  |
||
|
|
|