Not all applications report smooth % complete. So the calculation of time remaining involve the initial estimate as well. Given the bad information given for both % complete and initial estimate, there is no method of predicting how much longer the task will take that is completely right. The most reliable appears to be to combine the initial estimate the DCF (if in use for the project) the % complete, and the time spent already (the only really well known item in the list) to come up with an estimate.
-----Original Message----- From: boinc_dev [mailto:[email protected]] On Behalf Of Jon Sonntag Sent: Saturday, February 08, 2014 2:54 PM To: BOINC Developers Mailing List @berkeley.edu Subject: [boinc_dev] Estimated Time Remaining Why would 11% complete in 1.5 hours have an estimated 72 hours remaining when it should be closer to 14 hours remaining? Does BOINC need a math tutor? ;-) I find it interesting that the estimates on a Q6600 are correct but on both of my i7 hosts they are way too high. All hosts have all been running the app for several weeks so any learning curve by the smart estimate algorithm should have adjusted the numbers already, right? How long should it take BOINC to get the estimates correct? I would think less than an hour when percent complete is totally linear. Or is the problem the that the benchmarks do not take into account hyper-threading which skews the estimates? Jon Sonntag _______________________________________________ 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.
