If it is implemented on DDDT2, then I certainly haven't seen any announcement, nor how do you explain that I managed to get so many C types in the last 2 brief showers? (I only have the 1 dual core computer at my disposal)...

gb009761,

Not really... if the device qualifies it's just a question of the client having asked for work when it was in the pipe with enough seconds. The work goes out rather slow with 18mb a pop, so a client wont ask for work again until it knows what it has received / is receiving [at least that's what I observed]. I got a total of 6 on the HFCC/HCC/DDDT2 mix when sitting near a free-hotspot last week (of a McD) to report work completed off-line. Hotel room power is in the daily rate ;>)

edit: address as there came a poster in between whilst typing.

And NO, nothing was implemented to limit the amount of work per device queue, the work call is maxed at 15 per call. Personally I'd not be adverse to limiting the A-Type to 1 per core. Technically not sure it can be done for the B-Type given they're in the same feed as the C-Type... and of those there's still 22 million to come... we let the techs and scientists plod on the iron out the odd bugs, without pressurizing the vessel further to what they're already exposed to

Oh I know

Tuesday, still waiting on monday's rain...
am 8 days from gold, but my loss on DDDT2
is a gain for HFCC which is making a push
for sapphire.

BRING THE RAIN