Since the circumstances seem to be easier to re-create in the current SETI configuration (almost out of Astropulse work), would you like me to try for more [rr-sim] logs - and any other flags you care to suggest?
> Richard Haselgrove wrote: >> 17/04/2009 11:21:51 [wfd] target work buffer: 173664.00 sec >> 17/04/2009 11:21:51 [wfd] CPU: shortfall 0.00 nidle 0.00 est. delay 0.00 >> RS fetchable 100.00 runnable 500.00 > > It looks like the error is in rr_simulation(), not choose_project(). > The above two log lines are inconsistent. > "shortfall" is the number of idle CPU-seconds between now and now+173664. > "est. delay" is the length of time (starting now) that all CPUs are busy. > > It should never be the case that both of these are zero. > I.e., if shortfall is zero, all CPUs are busy until now+173664, > so est. delay should be at least 173664. > > The areas of code involved are rr_simulation(), > RSC_WORK_FETCH::accumulate_shortfall(), > and RSC_WORK_FETCH::update_estimated_delay(). > I'm looking at these but haven't found the problem so far. > > -- David > _______________________________________________ boinc_dev mailing list boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
