305794564 214381370 222870 7 Oct 2011 | 4:01:35 UTC 9 Oct 2011 | 3:03:58 UTC Completed, validation inconclusive 123,228.66 122,612.17 pending Woodall (LLR) v6.09 305543500 215685309 222870 7 Oct 2011 | 20:19:50 UTC 13 Oct 2011 | 0:54:14 UTC Completed, waiting for validation 182,590.16 181,715.39 pending Prime Sierpinski Problem (LLR) v6.09
That's a lot of possible pending credit.. it's taking forever to validate
Those are some big WUs. Seems like you're waiting on a wingman to finish his/her WU to verify your results - and they might have a lot slower computer than you, so it could take a day or so...
Or a month or so.Originally Posted by DrPop
Those are some big WUs. Seems like you're waiting on a wingman to finish his/her WU to verify your results - and they might have a lot slower computer than you, so it could take a day or so...
Yeah a month... annoyingI wish WUs done by fast system would only be sent out to other fast systems... but that would probably require some custom boinc server code.
Hmm...AQUA used to have some WUs that could only be given to rigs with quad core or higher. So, I know you could do something like that. Ahhh...you would have loved that project. Amazing CPU credits, best we ever had. Too bad they dropped it when DA's new credit scheme screwed their server code.
It's not just the speed of the system. Imagine a Core 2 machine with a queue length of 1 day, vs an SB with a queue of 10 days. The slower machine will return work faster. And then there is the issue of resends if the wingman doesn't return the task in time, or it doesn't match close enough requiring another wingman to break the tie. There is just no good way to do do what you want. Just lean back, have a beer, and get used to a delayed awarded credits. On the upside, you will continue to get credits after you have stopped crunching for that kind of project. So your c/d will be higher than usual during that transition period.Yeah a month... annoying
Posting Permissions
Reply With Quote
