Recently we got update from versions 7.00 and 7.02 to version 7.03 for many plan classes on SETI beta. Need to say I speak about those plan classes that existed both for old and new app version. That is, there was subversion update, just some edge cases fixes.
But this update completely ruined all already established performance estimates for upgraded plan classes. Situation became even worse than on initial app intruduction cause slowest CPU app stayed at version 7.00 and its estimates remained intact. Now absolute majority of SETI beta hosts recive tasks for slowest CPU app and no tasks for faster updated SIMD CPU apps. This means even longer delay for correct estimation generation. Estimate can be generated only when task completed and validated and it's not possible to complete task when scheduler simple doesn't send such tasks. In view of this please give attention to 2 separate BOINC server code issues: 1) Please make estimations transfer between app subversions for same plan class reliable. Already established estimations should be transferred and later auto-corrected if needed. 2) Please improve scheduler logic on initial stage of new app deployment when its real performance still unknown. Biggest attention requires the case when few different apps are possible for the same device. For example, when project supplies different SSE level apps for capable CPU. Currently scheduler tends to ignore some of available plan classes and not send tasks under them. I propose simple round-robin switching between eligible classes to ensure that particular device recived work under all possible plan classes and really has possibility generate results under all of them to provide data to BOINC servers for further performance estamitions generation. Currently (and some of our testers observed this in live testing) is possible to select suboptimal app as "base" app for device just because other apps did not get enough tasks to show their capabilities. -- Raistmer the Sorcerer _______________________________________________ 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.
