Page 1 of 1

6098 (1, 21, 309) core:0xa3 [Not] Bad

Posted: Fri Jan 25, 2013 4:08 pm
by art_l_j_PlanetAMD64
I dumped this WU: PRCG 6098 (1, 21, 309) core:0xa3

Same thing, no progress, no ETA, no Estimated PPD, no Estimated TPF.

This smp:2 (the lowly AMD Athlon 64 X2 Dual Core Processor 4200+) is now happily munching on PRCG 6338 (45, 26, 4):
ETA: 13 hours 22 mins
Base Credit: 163.00
Estimated Credit: 499.69
Estimated PPD: 895.71
Estimated TPF: 8 mins 02 secs
Assigned: 2013-01-25T15:35:59Z
Timeout: 2013-01-28T15:35:59Z
Expiration: 2013-02-01T15:35:59Z

Could the P6098 WUs, which have a Base Credit of 1593.00, be too much for this lowly CPU? Task Manager showed the normal thing for FahCore_a3.exe, namely 99% to 100% CPU Usage. Perhaps the CPU was unable to deconstruct the WU into its two cores? This system, despite its lowly CPU, has been able to complete all other (non-P6098) WUs well within the Timeout value, and getting a bonus from the QRB. I had never seen a P6098 WU before, on any system, until these two showed up today. Could this possibly be an AS issue, that WUs are assigned to systems that cannot work on them?

EDIT:
Sorry, bollix47, I was entering this (I guess) while you were answering the other report. I will wait longer in the future on the P6098 WUs. :oops:

Re: 6098 (1, 21, 309) core:0xa3 Bad

Posted: Fri Jan 25, 2013 4:14 pm
by bollix47
See my answer here.

Please stop deleting these work units ... you're adding a lot of time to the project.

Re: 6098 (1, 21, 309) core:0xa3 Bad

Posted: Fri Jan 25, 2013 4:16 pm
by art_l_j_PlanetAMD64
Yes, will do, please see my EDIT: above.

Re: 6098 (1, 21, 309) core:0xa3 Bad

Posted: Fri Jan 25, 2013 4:45 pm
by Joe_H
I have worked on earlier WU's from that series and processed them both on a 2.4 GHz Core 2 Duo system and on a 2.8 GHz i7. The ones from Project 6040 are comparable in size to the 6098, the TPF on the i7 at SMP:8 was about 15 minutes and an hour plus on the Core 2 Duo and took nearly 5 days. As the base points are a bit more on the 6098, I would expect the TPF on your system to be over an hour as well. That used to not be unusual, as long as your system can do a TPF of about 1:45 then the WU could be finished within the preferred deadline. The WS for these is set to a minimum SMP of 2, so the AS did correctly assign on that basis. If these do get assigned to systems unable to complete within the deadline, a suggestion can be made to require a greater SMP setting.

Re: 6098 (1, 21, 309) core:0xa3 Bad

Posted: Thu Feb 07, 2013 5:34 pm
by Joe_H
This WU has been successfully completed by another folder:
Hi ****** (team ******),
Your WU (P6098 R1 C21 G309) was added to the stats database on 2013-01-28 03:09:24 for 10184 points of credit.