I have 2 wus that have been running in excess of 6.5 hours and the time to finish is only 5.5. As there is no progress indicator for this project I'm loathed to abort them just in case I'm just being a touch too impatient.
Printable View
I have 2 wus that have been running in excess of 6.5 hours and the time to finish is only 5.5. As there is no progress indicator for this project I'm loathed to abort them just in case I'm just being a touch too impatient.
I've seen that happen, but not with those numbers, usually just overrun by 1/2 hour or so. Dunno... :scratch:
I just checked and it had uploaded, but took 7.5 hours to complete. I'm running 4 instances on a hyperthreaded dual Xeon rig so it may have overestimated the speed they would complete.
you could try switching off the hyperthread. If it's a RAM hog you may see an improvement :thumbs:
In a situation like that, you may also be losing big time to context switching.
Fozz, the program runs benchmarks on your system and that becomes the basis for the size of the task queue. Based on looking at the systems I'm running, the faster the system, the more it overshoots its estimate by. That would account for at least some, if not all, of the timing misfit you're seeing.