I have a workunit which has run for 2 hours 23 minutes and is only 2% complete. It says it will take 4 days and 21 hours to complete.

https://mindmodeling.org/workunit.php?wuid=20966706

I have another which has run for 25 minutes but is also still at 2%. Should I abort these workunits?

I have had a few of those recently. As far as I can tell, with only six hours to complete the task, they do not finish on time and are invalidated. All I see is them disappearing from BOINC, having wasted processing time.
I am not accepting new tasks until this is resolved.

It's because they sit at 2% for the whole crunching time. I've found that if you start a unit you will get credit for it, even if it is past the deadline. Generally units are taking up to 2.5 hours on my machine

As far as I can tell, once a work unit is past the deadline, it is re-sent to somebody else. Even if you have spent time processing it, whoever finishes first gets the credit.

Six hours seems rather short.

My machine has rocked the WUs in around an hour for all that ive done in the past few months and now all of the sudden they will not complete. I even let a few run for over a day and they did not complete. I will be suspending all Mindmodeling WUs until this issue is resolved

Brandon

Thanks for your help. Given your other comments, I will give it another try.

Wonderful I will keep up the crunching

Yeah, I just aborted a WU like this. It was suspended in RAM after the machine ran out of all available memory (Swap+Physical) and I think it's related to the growing memory issue.

The 2.5 hour timeout was actually put in probably more than a year ago as that has long been an issue on Windows machines. So the task isn't really finishing all the way, it's just hitting a self imposed time limit to keep them from running forever. Just let them run. They will all stop at 2.5 hours anyway and you get credit for them.

FYI: Got 3 tasks, two of which 'stuck' at those 2% and they are:
Native Python v2.7 Application (Windows Only) 1.10
- MindModeling_4972_1652956ab483fba0dc (estimated to complete (rising) 4days; ran for 2h already)
- MindModeling_4979_1653256ab496b90072 (same estimate)
(I'll let them 'expire' if you wish).

Third is about to complete in 3-3.5h (41% already) ... hmm or not (ran for 1h39m and 'stuck' at those 41.308%) :S
- MindModeling_4979_1653256ab5001c14f8

Task manager shows 3 python2.7.exe processes running full core each; RAM: 416'104K, 2x 23'684K respectively. Maybe it will help diagnose a problem. (RAM consumption doesn't increase)

Regards,
Atis

P.S. Suspending new job requests for now.

The 2.5 hour timeout was actually put in probably more than a year ago as that has long been an issue on Windows machines. So the task isn't really finishing all the way, it's just hitting a self imposed time limit to keep them from running forever. Just let them run. They will all stop at 2.5 hours anyway and you get credit for them.

Well it appears this may be happening again. I believe they do end up being solved around the two and a half hour mark regardless of what it says but something to note.

Just giving a heads up

Thanks guys!