One thing I have noticed when I upgrade one of my quad's from 6.6.23 to 6.6.25
was the scheduling decisions are clearly different.
When I upgraded it had one AP and one Einstein waiting to run. It was running
some other AP's and another Einstein along with a GPUgrid task. After the
upgrade the GPUgrid task got swapped out in favor of Seti MB (cuda). One of the
Einsteins got swapped in favor of another one. It still hasn't decided to
resume the GPUgrid task yet even though its done 4 Seti MB (cuda) since.
Another example I upgraded my i7 and apart from the 2nd GTX260 going MIA it
decided to swap out a couple of Seti MB (cuda) that it had running in favor of
a couple of other ones with earlier deadlines, but no indication of high
priority (it only keeps a 1 day cache).
I'm not saying its decisions are right or wrong, just that they are clearly
different to 6.6.23. I will keep an eye on them and let them crunch through
some of the other tasks.
Cheers,
MarkJ
Enjoy a better web experience. Upgrade to the new Internet Explorer 8
optimised for Yahoo!7. Get it now.
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
