I think this session should be marked as slow. I have a WU that is at ca. 61%, already runs for over 11 hours and none of my wingmen finished it yet although they have more cores as me. Progress of 0,001 per second and 100% core usage shows at least that it's not a stuck WU. ;-)

Edit:
As 1436 is the other side I guess it's the same there.

Edit 2:
Somehow I created two threads for this now. That wasn't intended, sorry... ;-)

---

Life is Science, and Science rules. To the universe and beyond
Proud member of BOINC@Heidelberg
My BOINC-Stats

Interesting, finished the WU first with almost 18 hours...

---

Life is Science, and Science rules. To the universe and beyond
Proud member of BOINC@Heidelberg
My BOINC-Stats

It does indeed seem to be a little slow. Not as slow as the other slow ones, but still slower than the fast ones. I've pushed it down the priority queue a bit.

There are something crazy here at frame 15 http://nr0.upanh.com/b1.s34.d3/25e178a708cda4d04c01c092179dc4f2_50426480.burp.png

---

This one certainly seems to be having a rough time... Lots of app crashes, aborted, over deadline, etc.

---

Click here to see My Detailed BOINC Stats

When I checked on Task 7321710 to see whether or not it been validated I saw that two copies of it had been but mine being marked as in valid because of this no credit has been granted. Validate state = invalid I have had a look at the task output and I cannot see anything that tells me why this task has marked as invalid. Is there any particular reason why this has been marked as invalid and will I get credit granted for my 6.19 hours of run time?Thanks in advance for explaining this situation

---

Have a crunching good day

This session has passed the record of sorts. We have processed 86% of it in a year.

---

Have a crunching good day

79% complete, 26 wall clock hours elapsed for a task, and many of those hours have used almost no CPU at all. 7 threads are allocated to this MT task, all sitting idle. My wingman did it in 146k CPU seconds. So my 7 thread machine should have been able to do that in about 6 hours. Should I abort?

Also odd, the task status on my host page:

17 Apr 2013 | 15:50:41 UTC 18 Apr 2013 | 9:50:41 UTC Timed out - no response

Less than a day deadline? That can't be right.

http://burp.renderfarming.net/workunit.php?wuid=1802444

---

Reno, NV
Team: SETI.USA

It turns out that BOINC will not let me suspend this one task, and request more tasks while waiting for a response. "Not requesting tasks: some task is suspended via Manager" Brilliant.

---

Reno, NV
Team: SETI.USA

79% complete, 26 wall clock hours elapsed for a task, and many of those hours have used almost no CPU at all. 7 threads are allocated to this MT task, all sitting idle. My wingman did it in 146k CPU seconds. So my 7 thread machine should have been able to do that in about 6 hours. Should I abort?

Also odd, the task status on my host page:

17 Apr 2013 | 15:50:41 UTC 18 Apr 2013 | 9:50:41 UTC Timed out - no response

Less than a day deadline? That can't be right.

http://burp.renderfarming.net/workunit.php?wuid=1802444

Judging that your wingman xPOD has finished this WU in about 6 hours you should have finished this WU in about 10-12 hours with your machine.
If it runs for over 26 hours now with this behaviour you can abort this task, because you probably hit the "never ending running task"-bug here, which happens from time to time to the Sunflower-WUs. Had this two or three times myself.

---

Life is Science, and Science rules. To the universe and beyond
Proud member of BOINC@Heidelberg
My BOINC-Stats