Message boards : Number crunching : Estimated remaining times a bit out of track
Author | Message |
---|---|
I know Matt knows this, but I would like to share my observations. | |
ID: 38555 | Rating: 0 | rate: / Reply Quote | |
Were you running with CPU allocated to the GPU tasks, or did you let the CPUMD tasks take all your CPU? | |
ID: 38557 | Rating: 0 | rate: / Reply Quote | |
Were you running with CPU allocated to the GPU tasks, or did you let the CPUMD tasks take all your CPU? Yes 5 threads where allowed to run CPU and 2 for the GPU's and 1 "spare". ____________ Greetings from TJ | |
ID: 38558 | Rating: 0 | rate: / Reply Quote | |
http://www.gpugrid.net/workunit.php?wuid=10159833 | |
ID: 38559 | Rating: 0 | rate: / Reply Quote | |
I know that, but am talking about the estimates of the GPU WU's. I have one that is 45% ready in 2 hours and estimated time is still 153 hours to go. Well within 3 hours it is finished. | |
ID: 38560 | Rating: 0 | rate: / Reply Quote | |
I'm seeing the same with the v8.47 applications released this morning. That's nothing to worry about - they seem to be running at the normal speed, so will finish at the normal time - it's just BOINC's notorious failure to get its estimates right for the first 101 tasks (overall) or 11 tasks (per host) after a new version is deployed. | |
ID: 38561 | Rating: 0 | rate: / Reply Quote | |
Task is running at normal speed with estimates all over the place- I can confirm- a GPU task at 91% complete--- estimated remaining time is 100hr-- a GPU task at 68% complete- estimated time is 200hr. I downloaded a Primegrid CPU Genefer task to see if affected and estimated time is triple of what task normally finishes. Before CPUMD tasks- all tasks had proper estimates for BOINC 7.4.21. Starting with an empty cache and having no tasks for BOINC. Estimates are still over the place. | |
ID: 38563 | Rating: 0 | rate: / Reply Quote | |
Strange issue is that I have run the CPU WU's on two rigs that also run the GPU WU's. With one rig the estimate times are normal again, at another rig it is still very long, more then 180 hours when starting. So that should indicate that a new version (8.47) is not the cause of it. Both rigs run with 8.47 since yesterday. | |
ID: 38568 | Rating: 0 | rate: / Reply Quote | |
Message boards : Number crunching : Estimated remaining times a bit out of track