On 10 June 2014 00:15, Shelby Melban <[email protected]> wrote: > I have some 8 core machines that get hot and the TThrottle app keeps my > CPU utilization down at times so my machine doesn't get overly hit. I very > often go over the estimated time to completion. My situation doesn't have > anything to do with android but I'm scared sometime that my results will be > flagged because they run longer than anticipated. >
Estimates are just that, estimates. It's ok if the runtime goes over the estimates. That can happen if the project didn't get the estimate quite right, you were using the computer for something or the computer had thermal issues and had to be slowed down. If you use TThrottle often BOINC should, over time, adjust to the new reality and give you longer estimates. Going over the estimate by some small-ish amount doesn't get your results flagged. However, if a task goes over the estimate so badly that BOINC's failsafe mechanism is triggered, then the task is aborted and marked invalid. This will reduce the host's daily quota and if there is lots of invalids the host won't be considered reliable any more. An invalid every now and then hurts one's ego but other than that it's harmless. But you happened to raise a good point. I believe TThrottle works by using OS level controls to suspend apps. When a task is throttled the elapsed time keeps counting normally and CPU time slower than normal. In case of CPU going in to thermal throttling mode the task's elapsed time and CPU time both count normally but the task will need more total CPU time. In both cases the task will make progress, just a bit slower than normally. When a task is killed for exceeding time limit neither case is considered. -Juha _______________________________________________ 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.
