TXR13,

When did the 2.516% [checkpoint] occur exactly? If your <checkpoint_debug> flag is on in the cc_config.xml, I'd like to see the series for this task, and given it's P3, it can't be to long a list.

Brinktastee,

Yours is more obvious. It immediately started on a tough position so it will stay on 0% until the position is complete. The algorithm will determine if to continue or end the trip for this task. If it decides to finish the task, the percent will jump to 100%. Follow comment by armstrdj about a coming change to introduce percent progress on long positions, not just at the end.

As always with Quorum projects, the place to ascertain how the wingman/wingmen fared is the WU Detail, one level deeper into the Result Status page.

edit: correct name armstrdj

hmmm, logic defying, I'd have expected this to finish right on the second position. Oh well, a new version was scheduled to do more refined % progress display anyhow.

21.61 hours for the second position where desired max length is 8 hours and the max overall not expected to exceed 10-12 hours. Maybe after all, P3 (or a P4 that has hyperthreading) on should be excluded from running this project, or an additional 'yes I read and understand the consequence' option before getting any more of these jobs.

Hmmm. This PC is mostly getting much higher credit than requested. The WUs' RSS are tiny and I suspect most code is running in cache, which is nice for (relatively) high clock speed CPUs. Over the last 40 HCMD2 WUs, the fastest machine this one has ever been paired with completed in 40% of the time (0.81 vs 2.03 hours). Average is about 70%. If the average (of fast machines, as it's mostly version 611 results) PC on WCG would take 15 hours, maybe all machines need the disclaimer!