I\'ve done a search and can\'t find this problem listed. If this is a duplication, I apologise. I have two BBC models running. Whilst checking resource share yesterday, I noticed that the two models were showing larger times to completion than the previous day. One model had 19:02:09 of CPU time during the 24 hours, the other 7:45:23. But as of 10:46 BST today each is showing almost an hour more to comletion than it was the previous day. Can someone tell me what is going on, please? The message file doesn\'t show any problems, nor does it show any extra download of work.

---

Experience with the 5.2 versions of BOINC suggests that they are a poor indicator of time to completion. Whether 5.3 and later will prove much better I\'m not sure but the best estimate will be the one you do yourself, taking % complete and actual CPU time as the basis.

The only reason to worry about time to completion increasing would be if the percentage complete actually fell - this can happen if your experiment hits a problem and has to go back to an earlier point, but there is nothing you can do about that.

If you are worried about how long the experiments wil take, you can set no new work in the projects tab and then suspend one of the tasks, letting the other run to completion.

---

Experience with the 5.2 versions of BOINC suggests that they are a poor indicator of time to completion. Whether 5.3 and later will prove much better I\'m not sure but the best estimate will be the one you do yourself, taking % complete and actual CPU time as the basis.

The only reason to worry about time to completion increasing would be if the percentage complete actually fell - this can happen if your experiment hits a problem and has to go back to an earlier point, but there is nothing you can do about that.

If you are worried about how long the experiments wil take, you can set no new work in the projects tab and then suspend one of the tasks, letting the other run to completion.

Thank you. I hadn\'t noticed (but should have) the disparity between CPU times & percentages. Using those times as a measure, my two models have 4000hrs and 4562 hrs to run (using 23 hrs per day to allow for backup etc.) instead of the 1800hrs and 1799 hrs listed. Quite a disparity!

---