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: 22
|
![]() |
Author |
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Mine has been doing it for the last few days (I had 6 days cache to do in only 7 calendar days). Some how it works it out to meet the deadline for all the WUs. All my DDDT2 WUs got in in time. Hopefully all my HCMD2 will as well. Cache set back to 2 days until Beta comes again. Patrick Patrick, if you run with 2 days, and Beta is announced, it's pointless to set a sky high cache. Devices only get per-beta/science 1 task per processor thread i.e. a quad gets 4 and in the last concurrent GFAM/DSFL beta you get at most 8. Then when the result is reported you can get a replacement, but then if you had 8, what's the chance of there still being regular beta results left? Only few repairs and no replies on a good beta, and on a bad beta... waste of time. The last DDDT2 B-Type (all B-Type) have an original deadline of 8 days... that's why your client made it, probably ;>) --//-- |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
ty sek i will change
|
||
|
|
![]() |