Well gulftown has two extra cores and 4 extra threads to handle it.
Think I might be "upgrading" to a 970 at least on weebeastie at some point in the rebuild.
An example of what I was talking about before, on my main rig, I set the GTX460 folding and everything seemed ok for a while with the bigadv but it wasn't really.
Here is the log before I started the GTX folding, not great PPD but the machine gets used for other things as well as folding:
[09:07:40] Completed 202500 out of 250000 steps (81%)
[10:01:19] Completed 205000 out of 250000 steps (82%)
[10:54:47] Completed 207500 out of 250000 steps (83%)
[11:48:10] Completed 210000 out of 250000 steps (84%)
[12:40:46] Completed 212500 out of 250000 steps (85%)
[13:33:30] Completed 215000 out of 250000 steps (86%)
[14:25:53] Completed 217500 out of 250000 steps (87%)
So around 50 min/frame, not great but the WU was a toughie. When left to its own devices it drops down to around 38-40 min/frame or aprox 21K PPD
Then I started the GTX460
[02:44:27] Completed 222975 out of 250000 steps (89%)
[04:56:26] Completed 225000 out of 250000 steps (90%)
[07:57:33] Completed 227500 out of 250000 steps (91%)
[08:43:45] - Autosending finished units... [September 1 08:43:45 UTC]
[08:43:45] Trying to send all finished work units
[08:43:45] + No unsent completed units remaining.
[08:43:45] - Autosend completed
[11:11:03] Completed 230000 out of 250000 steps (92%)
[14:13:33] Completed 232500 out of 250000 steps (93%)
[14:43:42] - Autosending finished units... [September 1 14:43:42 UTC]
[14:43:42] Trying to send all finished work units
[14:43:42] + No unsent completed units remaining.
[14:43:42] - Autosend completed
And thats the last I have heard from it, its gone to 3h+ per frame and often looks like its hung. CPU usage is still at 100% with about 85% on the CPU folding process, about 1-2% on the GPU folding process and the rest taken up by "system" which I have traced down to acpi.sys with a process tracker.
This is running "-smp 7 -bigadv -forceasm -verbosity 9" cpu client is running slightly lower priority than gpu as per the -configonly switch.
I've also tried various affinity programs, WinAFC which worked well for GPU2 and A3 SMP doesn't seem to help at all with this situation on this machine.
When running WinAFC or any other program I've usually allocate CPU0-6 to the SMP client and CPU7 to the GPU client.
What concerns me is the acpi.sys CPU usage it doesn't start straight away it builds up over time but stays hovering around 10% across all cores.
