Folding Forum

Posted: **Fri Feb 12, 2010 6:00 pm**

I have now gotten a few of the 6015 WU's that appear to be extremely slow, taking hours to complete just 1%. In the task manager there appear to be 2 FahCore_a3.exe 's, each with 50% CPU utilization, and my CPU temperatures are at where they usually are when folding so IDK whats going on.

Core i7 920
Win7 x64

WIn SMP 6.29 client

Code: Select all

[07:15:40] Completed 5000 out of 500000 steps  (1%)
[09:17:55] Completed 10000 out of 500000 steps  (2%)
[11:28:23] Completed 15000 out of 500000 steps  (3%)
[13:21:55] Completed 20000 out of 500000 steps  (4%)
[15:15:17] Completed 25000 out of 500000 steps  (5%)
[17:09:24] Completed 30000 out of 500000 steps  (6%)
[17:21:42] Killing all core threads
[17:21:42] Killing 4 cores
[17:21:42] Killing core 0
[17:21:42] Killing core 1
[17:21:42] Killing core 2
[17:21:42] Killing core 3

Folding@Home Client Shutdown at user request.
[17:21:42] ***** Got a SIGTERM signal (2)
[17:21:42] Killing all core threads
[17:21:42] Killing 4 cores
[17:21:42] Killing core 0
[17:21:42] Killing core 1
[17:21:42] Killing core 2
[17:21:42] Killing core 3

Folding@Home Client Shutdown.

Here is the Benchmark from FAHMon:

Code: Select all

 Project : 6015
 Core    : Unknown
 Frames  : 100
 Credit  : 484


 -- WinSMP --

 Min. Time / Frame : 1h 54mn 07s  - 61.07 ppd
 Avg. Time / Frame : 1h 54mn 07s  - 61.07 ppd
 Cur. Time / Frame : 1h 54mn 07s  - 61.07 ppd
 R3F. Time / Frame : 1h 54mn 07s  - 61.07 ppd
 Eff. Time / Frame : 2h 45mn 50s  - 42.03 ppd

I tried deleting everything FAH related and making sure I had the correct checksum but the whole thing starts over again taking around 2 hours per %.

Posted: **Sat Feb 13, 2010 3:46 am**

Did you configure the client as a service? Or are you purposely running two copies of the SMP client and with -smp 4 / -smp 3?

Either way, it is bad to run two clients; most people run the A3 core with -smp 7 or 8, spawning a single instance of Fahcore_a3. If that's what you did as well, then exit the currently running client, and terminate the remaining FahCore_a3 process. It might be a rogue or somehow locked up from an previous exit.

Posted: **Thu Feb 18, 2010 9:45 pm**

I deleted the work units and haven't gotten 6015 since then. Might have just gotten a string of bad WUs.

Folding Forum

P6015 (R1, C142, G6), extremely slow

P6015 (R1, C142, G6), extremely slow

Re: P6015 (R1, C142, G6), extremely slow

Re: P6015 (R1, C142, G6), extremely slow