| 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: 13
|
|
| Author |
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
Additional work had crossed my mind, since on the 22nd there was well more results validated than the 20st/21nd, infact more than the 2 days combined. Could also be a big bufferer holding up validations, so yes it would be interesting to get a hard data breakdown rather than a pile up of inferences and deductions.
|
||
|
|
Seoulpowergrid
Veteran Cruncher Joined: Apr 12, 2013 Post Count: 823 Status: Offline Project Badges:
|
It could also be from a single large thread server or a pair of servers that was offline for a week. I use one 32 thread server and frequently have 25 pages of queue (default queue size) so around 375 tasks. Spread over the server and a couple smaller machines I think I got around 500 WUs total during the 10k resupply.
----------------------------------------A WCG zero redundant project. Are redundancies created based on machine reliability? Then is there a way that machines could lose their status as a "good/reliable" machine if enough time went by? Could that have caused such high numbers? ![]() |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
'Return' reliability does not expire and is reflective of its recent history average... One time incidents won't blow this, but for errors. Officially, when a new app version is loaded, the need to proof resets, but if for same science, the techs have blocked that reset...so reliability is at science level, not WCG total.
|
||
|
|
|