I didn't mean to imply that no checks would be needed. What's known is that the original app_version/result pairing was fully vetted, so less checking is needed. The current logic could be used if the host isn't asking for work for the same resource.
IMO there's a high probability that the host will still be asking for work for the same device simply because most hosts are only participating in one project. Although credit_per_cpu_sec is no longer a useful cross-project comparison of credit rates, the table at http://boinc.netsoft-online.com/e107_plugins/boinc/get_cpcs.php also shows the number of active hosts which are shared between projects, and in general the total shared with other projects is far less than the total active on the project, shown where the project's row and column intersect. There are exceptions for some small projects and projects which don't have work all the time, of course. -- Joe On Thu, 08 Nov 2012 15:53:29 -0500, David Anderson <[email protected]> wrote: > > > On 08-Nov-2012 12:37 PM, Josef W. Segur wrote: >> Some notes on the changes. > ... >> - Adding the explicit wu_is_infeasible_custom() call is redundant, that has >> been >> called in wu_is_infeasible_fast() since late July 2009. > > Thanks; I removed this. > >> >> - I'm disappointed you didn't take the opportunity to make use of >> result.app_version_id to try to resend for the same app_version as the >> original >> assignment chose. That should be feasible in the vast majority of cases, and >> users could easily understand the logic. > > ?? the original app version could use a resource for which no work is needed; > that was the motivation for the change. > > -- David _______________________________________________ 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.
