Excellent - a red letter day indeed! Many thanks to all those involved.

Outstanding
 

Fasther throughput on i5 (bottlnecked with 4 instances using 0.19)
CPU doesn't even throttle up (power draw 6.4 watts)
LOWER overall system power consumption by 100 watts!



OUTSTANDING RESULTS!

Oh and nvidia 310.90 just came out.

Geforce 560, option by default, 200 Ghz-d by day

Still running -st2 on both GPUs. GTX 570 at about 55%, 460 about 75%. Affinity not set. CPU at about 20-25%. The 570 finished. With the 460 still running it's pulling 10-12% CPU.

EDIT: Now running an assignment on the 570, and there is negligible CPU usage for that instance. Just -st2 is using more CPU.

[QUOTE=kladner;323872]Still running -st2 on both GPUs. GTX 570 at about 55%, 460 about 75%. Affinity not set. CPU at about 20-25%. The 570 finished. With the 460 still running it's pulling 10-12% CPU.[/QUOTE]

-st/-st2 tests both, CPU-sieve and GPU-sieve kernels.

Oliver

[QUOTE=swl551;323869]Fasther throughput on i5 (bottlnecked with 4 instances using 0.19)
CPU doesn't even throttle up (power draw 6.4 watts)
LOWER overall system power consumption by 100 watts!



OUTSTANDING RESULTS!

Oh and nvidia 310.90 just came out.[/QUOTE]

I upgraded to 310.70 two weeks ago, and it gave me slightly poorer performance (with the non-GPU sieving mfaktc) than the earlier 306.97 version. I reverted back to the earlier version. I guess I could change drivers again with this new mfaktc and see what the results are.

Chuck

[QUOTE=Chuck;323878]I upgraded to 310.70 two weeks ago, and it gave me slightly poorer performance (with the non-GPU sieving mfaktc) than the earlier 306.97 version. I reverted back to the earlier version. I guess I could change drivers again with this new mfaktc and see what the results are.

Chuck[/QUOTE]

310.70 had a short life, suggesting it did have some problems.

[QUOTE=swl551;323869]Oh and nvidia 310.90 just came out.

310.70 had a short life, suggesting it did have some problems. [/QUOTE]

That's very good to know. Thanks! I'm running 310.70, but will upgrade.

@ Oliver- Thanks for the explanation. I'm now running assignments on both cards:

[CODE]64.8M 69-73 assignments -both cards
GTX 570 6.004s 415 GHz-D/D GPU 95% 823 MHz 71 C
GTX 460 12.135s 205 GHz-D/D GPU 98% 830 MHz 70 C
[/CODE]

CPU is essentially idle.

The temperatures above are about 2-3 C higher than with 4 instances of mfaktc 0.19 on the 570, and 2 instances on the 460. Considering that the CPU is idle, they seem to be working harder. On the other hand, a cool CPU means that the case fans throttled back.

This looks like a big jump in throughput, and I haven't even gotten P95 running yet. I now have up to six cores to run P-1, or something. :smile:

comparison
 

0.19 running 4 instances on GTX-570 988mv@850mhz with i7-2600k @ 4.2ghz
yielded [B] 118[/B]ghzDay per instance = [B]472[/B]ghzDay total


0.20 running 1 instance on GTX-570 988mv@850mhz with i7-2600k @ 4.2ghz
yielding [B]427[/B]ghzDay. [U]down [B]45[/B]ghzDay[/U]


However on my i5 2500k 0.20 increased by [B]25[/B]ghzDay compared to 0.19. (cpu was bottlenecked)

[QUOTE=swl551;323882]
0.20 running 1 instance on GTX-570 988mv@850mhz with i7-2600k @ 4.2ghz
yielding [B]427[/B]ghzDay. [U]down [B]45[/B]ghzDay[/U]
[/QUOTE]

But now maybe you can run something on the cpu! :max:

EDIT: Er, that is using the part of da cpu that 0.19 *used* to take.

With 6x 0.19 on the 570, and 2x on the 460 I was getting a combined GHz-D/D of 530-535 (per mfaktc readings). With 2.0 (32 bit -slightly better than 64 bit) those mfaktc readings total about 625 GHz-D/D with 1 instance per GPU. I now have 5 workers running P-1 in P95. This last item did not seem make any difference in the mfaktc 2.0 performance.

EDIT: [OT]PrimeNet still keeps sticking in 1 DC assignment (Worker #3) to 4 P-1s in P95. All the settings I can find, both online and in P95, are set to P-1. I have worked around this by moving all the assignments from the other 4 workers to Worker #3. This stops #3 from getting more assignments for now, and the other 4 then fill in with P-1s.[/OT]

EDIT2: Sieve is running 82,485 on both GPUs, with SievePrimesAdjust=1. Otherwise the settings are default except for CheckpointDelay=300, Stages=0, and StopAfterFactor=2.