Is there something wrong with the new MJHARVEY WUs?

It seems to need wide! over! 30h to complete on 560TI (running @ 98% and full standart clockspeed). And that in the short Queue! O.o Aborted now 4 of them..

---

DSKAG Austria Research Team: http://www.research.dskag.at

I've got the same problem with these MJHARVEY WU's. Four of them have been running 14 hours, and only 28% complete. This is on GTX 295 @ 1081GFLOPS Peak. I'm monitoring the GPU clocking with GPU Shark, and the GPU's have not downclocked. Please let me know what's up with these WU's. Rick

---

And much the same here - my first is at about 15% after 12 hours, on a shared GTX 470.

Even in the count=0.5 configuration, that card can usually do two or three short-queue tasks per day - I think these MJHARVEYs belong in the long queue, at least.

Yup.. also a ~30 hour WU here for me. 12 hours @ 30% completion on a GTX 570. Wow.

Sorry all, I made a mistake in their configuration. They're deleted now and will be resubmitted later.

MJH

Deleted and mistake as in even the one that I have at 74% completion after 28h is worthless?

As well, 20 hours per unit spins to the trash, i do not even a little bit of grace.

Sorry all, I made a mistake in their configuration. They're deleted now and will be resubmitted later.

MJH

Are you sure? I've just aborted WU 3359817 (unstarted in my cache, stuck behind a running one after 24 hours), and a replacement task has been created and put on the queue for sending out.

I'm pulling my cards off GPUGRID until this is sorted out. I can't "afford" to waste 30 hours of work for nothing. And, yes, theses are still downloading.

As of 11:00 Eastern Daylight Time on 22.April.2012, I'm also still getting these Ultra Long MJHArvey WU's. They seem to be wingman WU's (_3) rather than originals. Also note however, I'm also getting NEW MJHARVEY WU's that are NOT ultralong. Moderator, PLEASE LET US KNOW WHAT"S GOING ON! Rick

---

I had 2 harvey wus that ran over 24 hours each and errored out. I do not accept long run wu's and these definitely seem to qualify so I don't know why I got them in the first place, but now I have to babysit my computer and abort them manually. Think it's time to move my GPUs to another project til they get this figured out.

Some Wus will escape cancelling (for instance all the ones aborted).
I have done another round of cancellations.

Let me know if you still received those.

gdf

Well, mine got the message OK:

22/04/2012 18:33:01 | GPUGRID | Sending scheduler request: Requested by project.
22/04/2012 18:33:04 | GPUGRID | Result 19x45-MJHARVEY_FRAGXA3-0-30-RND6951_0 is no longer usable
22/04/2012 18:33:04 | GPUGRID | [sched_op] Reason: Unrecoverable error for task 19x45-MJHARVEY_FRAGXA3-0-30-RND6951_0 (aborted by project - no longer usable)
22/04/2012 18:33:36 | GPUGRID | Sending scheduler request: To report completed tasks.
22/04/2012 18:33:36 | GPUGRID | Reporting 1 completed tasks, not requesting new tasks
22/04/2012 18:33:38 | GPUGRID | [sched_op] handle_scheduler_reply(): got ack for task 19x45-MJHARVEY_FRAGXA3-0-30-RND6951_0

and since then I've picked up new work from different - normal-sized - tasks.

The fragxa3 would have reached about 38% in 29 hours by then (I'd checked it not long before), but is still showing unreported on the website: task 5268502

Oh man thats bad, would be interesting when we can compute short units again on unattended machines :/

---

DSKAG Austria Research Team: http://www.research.dskag.at