Agreed. But by convention, and IIRC by default, rsc_fpops_bound is set to 10x rsc_fpops_est: that allows the client to kill over-running (infinite loop?) tasks with a fair degree of safety.
With good estimates, and a 10x bound, viable tasks run to term, and loopers get killed. That's how it should be. If estimates are bad, and the bound remains at 10x, projects have found viable tasks being killed for over-running. The better solution for that is to correct the estimates: the alternative (raising the bound multiplier) risks loopers wasting even more time and power. >________________________________ > From: Nicolás Alvarez <[email protected]> >To: Richard Haselgrove <[email protected]> >Cc: BOINC Developers Mailing List <[email protected]> >Sent: Tuesday, 18 February 2014, 16:05 >Subject: Re: [boinc_dev] Estimated Time Remaining, frictional reporting ... > > >There are two different values, rsc_fpops_bound is used for the resource >limit, and rsc_fpops_est is used for the estimated time and progress. So >wanting to avoid 'resource limit exceeded' errors has nothing to do with >providing a good estimate. > >El lunes, 17 de febrero de 2014, Richard Haselgrove < >[email protected]> escribió: > >> Unfortunately, some projects take the easy cop-out - applying a massive >> rsc_fpops_bound to circumvent resource limit exceeded, instead of resolving >> it properly from first principles. >> >> I suspect that some of the smaller projects have enough on their plate >> getting their heads round their own scientific research needs, and don't >> have enough time and energy left to switch into "computer scientist" mode >> and concentrate on the boincification of their application and workflow. >> >> >> >> >________________________________ >> > From: Oliver Bock <[email protected] <javascript:;>> >> >To: David Anderson <[email protected] <javascript:;>>; Rytis >> Slatkevičius <[email protected] <javascript:;>> >> >Cc: BOINC Developers Mailing List <[email protected]<javascript:;> >> > >> >Sent: Monday, 17 February 2014, 9:22 >> >Subject: Re: [boinc_dev] Estimated Time Remaining, frictional reporting >> ... >> > >> > >> >On 14/02/14 8:30 , David Anderson wrote: >> >> I'd prefer to figure out why the static estimates are off. >> >> If an app's jobs are of a size proportional to wu.rsc_fpops_est, >> >> the static estimates should be almost exact, even for a host's first >> jobs. >> > >> >The static estimates are often very rough ones because it's sometime not >> >that easy to get a handle on accurate ones. In the extreme the estimate >> >gets just set in such a way that you don't run into a "resource limit >> >exceeded" issue - so you add at least some headroom. However, even in >> >such a case you may know that your app will behave more or less linear. >> >This is why I think having the said opt-in flag would be very useful for >> >such apps. >> > >> > >> >Cheers, >> >Oliver >> > >> > >> > >> >_______________________________________________ >> >boinc_dev mailing list >> >[email protected] <javascript:;> >> >http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev >> >To unsubscribe, visit the above URL and >> >(near bottom of page) enter your email address. >> > >> > >> _______________________________________________ >> boinc_dev mailing list >> [email protected] <javascript:;> >> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev >> To unsubscribe, visit the above URL and >> (near bottom of page) enter your email address. > > > >-- >Nicolás >_______________________________________________ >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. > > _______________________________________________ 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.
