World Community Grid - View Thread - Strange BOINC Priority

Thanks for the feedback Uplinger

This thread started off life as an observation so yep it's just nitpicking as all WU's do get crunched very successfully

Bizarrely my latest batch are doing the exact opposite !

I aborted my whole queue (209 WU's [:">) so that sorting would not have an effect but the scheduler threw me a curve ball with some short expiry time HFCC's so it's been a while to get back to this point

I've just completed those

So here's what it's doing without any sort button being pressed

Not wrong, just different to how we've seen BOINC working since we migrated across to it back in early 2006.

Keep 'em crunching

Dave

PS, If those are freshly received tasks in an empty cache, due on the 4 of September, then that infers 8 days deadline. There are no 8 day deadline tasked for HFCC or C4CW AFAIK, it's 10 days or rush jobs 4 days. Something does not rhyme here, someone playing with the joystick maybe, as when my quad received same jobs today, they still had 10. Here's 4 from my queue right around the same timestamp:

c4cw_ target01_ 358990653_ 0-- 1292373 In Progress 27-8-10 08:20:21 6-9-10 08:20:21 0.00 0.0 / 0.0
c4cw_ target01_ 357668247_ 0-- 1292373 In Progress 27-8-10 08:11:54 6-9-10 08:11:54 0.00 0.0 / 0.0
c4cw_ target01_ 353371672_ 0-- 1292373 In Progress 27-8-10 06:49:15 6-9-10 06:49:15 0.00 0.0 / 0.0
c4cw_ target01_ 353595800_ 0-- 1292373 In Progress 27-8-10 06:49:15 6-9-10 06:49:15 0.00 0.0 / 0.0

hmmm, maybe a miraculous retrieval of lost tasks... the servers would resend those to the same client.

BTW 8 days deadline and HP processing suggests your client is (still) over-cached or processing tasks slower than normal. A project reset would restore the DCF back to 1.000000. Might help to restore normalilty.