For the last few weeks, it looks as if the SETI@home server has been making strange plan_class choices.
Here's a screen-shot taken this afternoon. http://img46.imageshack.us/img46/1426/cudaorcuda23.png There seem to be almost as many tasks assigned to plan class 'cuda' as there are to plan class 'cuda23': on this project, both are compatible with the card in use, but cuda23 is usually significantly faster, so should be chosen in preference when available. The two tasks I've picked out in red have different runtime estimates, but exactly the same deadline, so they must have been allocated in the same scheduler RPC. Looking at the datestamps on the executable files in the project directory, it appears as if this started happening around 9th. November (I use European date ordering) Directory of D:\BOINCdata\projects\setiathome.berkeley.edu 09/11/2011 21:46 1,445,888 setiathome_6.08_windows_intelx86__cuda.exe 07/10/2011 06:13 2,859,008 setiathome_6.09_windows_intelx86__cuda23.exe I normally run optimised applications on this host, but de-optimised in late September or early October. So I'm pretty certain that all the 519 completed tasks for 'SETI@home Enhanced 6.08 windows_intelx86 (cuda)' have been run in the last four weeks. http://setiathome.berkeley.edu/host_app_versions.php?hostid=3751792 That's too many to expect for the planned random test that the relative speeds are as expected. _______________________________________________ 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.
