Author |
Message |
|
In the last week or so I've noticed the the opt_ work units get to 100%. Instead of being reported the sttus remains at "Running", and continue to add CPU time to the total, while the time remaining is at "--".
I've tried rebooting the computer, restarting Boinc, suspending and restarting the task, but nothing gets it to the Ready to Report state.
I want to continue doing these work units, but have only been able to start new ones by aborting them.
____________
|
|
|
In the last week or so I've noticed the the opt_ work units get to 100%. Instead of being reported the sttus remains at "Running", and continue to add CPU time to the total, while the time remaining is at "--".
I've tried rebooting the computer, restarting Boinc, suspending and restarting the task, but nothing gets it to the Ready to Report state.
I want to continue doing these work units, but have only been able to start new ones by aborting them.
The calculation of the percentage of completion is inaccurate, and fails to show much about the time required to reach the original completion time estimate. However, I've found that on my machine, the actual time required for these workunits to complete is about 2.5 CPU hours, so I only worry about such workunits if they go significantly longer than this.
|
|
|
In the last week or so I've noticed the the opt_ work units get to 100%. Instead of being reported the sttus remains at "Running", and continue to add CPU time to the total, while the time remaining is at "--".
I've tried rebooting the computer, restarting Boinc, suspending and restarting the task, but nothing gets it to the Ready to Report state.
I want to continue doing these work units, but have only been able to start new ones by aborting them.
Same problem exactly. No Joy.
____________
Hello from Davao City - Best Place in the Philippines.
Formerly of Evanston, IL, Zion, IL, Aurora, IL, Hendersonville, TN
|
|
|
In the last week or so I've noticed the the opt_ work units get to 100%. Instead of being reported the sttus remains at "Running", and continue to add CPU time to the total, while the time remaining is at "--".
I've tried rebooting the computer, restarting Boinc, suspending and restarting the task, but nothing gets it to the Ready to Report state.
I want to continue doing these work units, but have only been able to start new ones by aborting them.
Same problem exactly. No Joy.
The message in between you two folks, the part of the OPT program does not report the percentage completed properly, just part of the way it works. It could be at 50% and say 100%, when it is done, mas 2 1/2 hours it will be done and report and you will start crunching another unit. Now the 2 1/2 hours is a bit flexible but will be within a few minutes or so. I have had some in the past go up to about 5 minutes over.
____________
|
|
|
In the last week or so I've noticed the the opt_ work units get to 100%. Instead of being reported the sttus remains at "Running", and continue to add CPU time to the total, while the time remaining is at "--".
I've tried rebooting the computer, restarting Boinc, suspending and restarting the task, but nothing gets it to the Ready to Report state.
I want to continue doing these work units, but have only been able to start new ones by aborting them.
Same problem exactly. No Joy.
The message in between you two folks, the part of the OPT program does not report the percentage completed properly, just part of the way it works. It could be at 50% and say 100%, when it is done, mas 2 1/2 hours it will be done and report and you will start crunching another unit. Now the 2 1/2 hours is a bit flexible but will be within a few minutes or so. I have had some in the past go up to about 5 minutes over.
____________
Hello from Davao City - Best Place in the Philippines.
Formerly of Evanston, IL, Zion, IL, Aurora, IL, Hendersonville, TN
|
|
|
In the last week or so I've noticed the the opt_ work units get to 100%. Instead of being reported the sttus remains at "Running", and continue to add CPU time to the total, while the time remaining is at "--".
I've tried rebooting the computer, restarting Boinc, suspending and restarting the task, but nothing gets it to the Ready to Report state.
I want to continue doing these work units, but have only been able to start new ones by aborting them.
Same problem exactly. No Joy.
The message in between you two folks, the part of the OPT program does not report the percentage completed properly, just part of the way it works. It could be at 50% and say 100%, when it is done, mas 2 1/2 hours it will be done and report and you will start crunching another unit. Now the 2 1/2 hours is a bit flexible but will be within a few minutes or so. I have had some in the past go up to about 5 minutes over.
PERHAPS, but mine has been waiting for and going past for six hours. JSB
____________
Hello from Davao City - Best Place in the Philippines.
Formerly of Evanston, IL, Zion, IL, Aurora, IL, Hendersonville, TN
|
|
|
In the last week or so I've noticed the the opt_ work units get to 100%. Instead of being reported the sttus remains at "Running", and continue to add CPU time to the total, while the time remaining is at "--".
I've tried rebooting the computer, restarting Boinc, suspending and restarting the task, but nothing gets it to the Ready to Report state.
I want to continue doing these work units, but have only been able to start new ones by aborting them.
The calculation of the percentage of completion is inaccurate, and fails to show much about the time required to reach the original completion time estimate. However, I've found that on my machine, the actual time required for these workunits to complete is about 2.5 CPU hours, so I only worry about such workunits if they go significantly longer than this.
I waited for the next one to go to 2.5 hours, and it did report. The next one did the same. So on my PC it is simply the reporting of the % is incorrect. thanks for pointing this out.
|
|
|
In the last week or so I've noticed the the opt_ work units get to 100%. Instead of being reported the sttus remains at "Running", and continue to add CPU time to the total, while the time remaining is at "--".
I've tried rebooting the computer, restarting Boinc, suspending and restarting the task, but nothing gets it to the Ready to Report state.
I want to continue doing these work units, but have only been able to start new ones by aborting them.
Same problem exactly. No Joy.
The message in between you two folks, the part of the OPT program does not report the percentage completed properly, just part of the way it works. It could be at 50% and say 100%, when it is done, mas 2 1/2 hours it will be done and report and you will start crunching another unit. Now the 2 1/2 hours is a bit flexible but will be within a few minutes or so. I have had some in the past go up to about 5 minutes over.
PERHAPS, but mine has been waiting for and going past for six hours. JSB
Are you crunching exclusively for Malaria? If not that could be the problem, 6 hours, with time out for other projects, would not be too far out of line. And if you are doing several others, then you are well within the 2.5 hours. Every 60 minutes it switches by default, so if you are doing 2 projects, that is only 3 hours for Malaria and 3 hours for the others projects. If you are doing 3 projects, that is only 2 hours for each. If you are only doing Malaria and also crunching 24/7 you may want to just turn off the OPT units in your settings.
____________
|
|
|
In the last week or so I've noticed the the opt_ work units get to 100%. Instead of being reported the sttus remains at "Running", and continue to add CPU time to the total, while the time remaining is at "--".
I've tried rebooting the computer, restarting Boinc, suspending and restarting the task, but nothing gets it to the Ready to Report state.
I want to continue doing these work units, but have only been able to start new ones by aborting them.
The calculation of the percentage of completion is inaccurate, and fails to show much about the time required to reach the original completion time estimate. However, I've found that on my machine, the actual time required for these workunits to complete is about 2.5 CPU hours, so I only worry about such workunits if they go significantly longer than this.
I waited for the next one to go to 2.5 hours, and it did report. The next one did the same. So on my PC it is simply the reporting of the % is incorrect. thanks for pointing this out.
No problem, hopefully all is going well now.
____________
|
|