3# as well, even if i'm not really active on Gpu front at this time

#3 for me, even if I used mmff 0.26 with no -gs switch, and it appeared to sieve on GPU.

Luigi

[QUOTE=axn;322637]Intelligent/Smart option -- Do a selftest and pick the one with highest thruput.[/QUOTE]I'm not sure if that would differ from #3 -- I'm not sure if there are cases where GPU sieving would be [i]slower[/i] that CPU sieving. Possibly on a very-slow GPU (GT 620 or similar) with a very fast CPU -- I'm not sure if Oliver/George have looked into the cutoff points of efficiency.

It has been determined that CC 1.x GPUs have poor throughput for GPU sieving to the point where it makes no sense so it's never available, but for CC 2.0+ the benefit is significant.

The value for GPUSievePrimes [i]might[/i] be a viable target for auto-adjustment, but in brief testing I found very little difference in throughput using different values.

Can somebody give an rough indication of when the 0.20 'production' client will be released? I know it is all done in your spare time, but I (and probably others) are eagerly waiting for this big improvement.

Hello,

[QUOTE=James Heinrich;322680]I'm not sure if that would differ from #3 -- I'm not sure if there are cases where GPU sieving would be [i]slower[/i] that CPU sieving. Possibly on a very-slow GPU (GT 620 or similar) with a very fast CPU -- I'm not sure if Oliver/George have looked into the cutoff points of efficiency.
[/QUOTE]

OK, we have a winner: option #3. :smile:
No, no automatic switching between CPU and GPU sieving, I like simple solutions.

Oliver

[QUOTE=VictordeHolland;322687]Can somebody give an rough indication of when the 0.20 'production' client will be released? I know it is all done in your spare time, but I (and probably others) are eagerly waiting for this big improvement.[/QUOTE]

When it's done! :yucky:

Oliver

P.S. I [B]want[/B] to finish v0.20 this year. Add a week or two for testing where I give it to a few people and if no problems are found I'll release it.

Hey guys,

Got a new 670GTX (upgrade from 460GTX). I am now cracking at approx 195-200M/s (vs 150M/s) which is pretty poor given the upgrade. NV really made the new chip a pure gaming chip with crappy compute performance and its really showing.

The only advantage I know would be this GPU uses similiar power vs the 460GTX (if not only slightly more).

Does mfaktc work on dual GPU systems with separate GPU? How does one assign each GPU (if this is possible). I was thinking of plugging in the 460GTX purely for compute use? What do you guys think?

Yes, you can plug both of them in, and depending on your CPU, use more instances of mfaktc for each.
Use the "-d x" switch to say which GPU be used by which instance, substitute x with the gpu number. Is in the docs, and right in this very thread too, few pages back.

Stupid Question
 

Where is the program for windows 7 x64?

I KNOW that it is a stupid question. I am too lazy to go through 86 pages of posts.

[QUOTE=Sutton Shin;322807]Where is the program for windows 7 x64?

I KNOW that it is a stupid question. I am too lazy to go through 86 pages of posts.[/QUOTE]

Very stupid. Even if you're too lazy to go through posts, [URL="http://lmgtfy.com/?q=mfaktc"]Google is your friend[/URL]. (First or third link are perfectly useful.)

:google:

[QUOTE=LaurV;322806]Yes, you can plug both of them in, and depending on your CPU, use more instances of mfaktc for each.
Use the "-d x" switch to say which GPU be used by which instance, substitute x with the gpu number. Is in the docs, and right in this very thread too, few pages back.[/QUOTE]

In other words, RTFM.


____________________________________________________________________________
:razz:

[QUOTE=xtreme2k;322805]Hey guys,

Got a new 670GTX (upgrade from 460GTX). I am now cracking at approx 195-200M/s (vs 150M/s) which is pretty poor given the upgrade. NV really made the new chip a pure gaming chip with crappy compute performance and its really showing. [/QUOTE]

Well, you're limited by your CPU, a single core can't feed your GTX 670. You can either start a second instance using a second CPU core our wait for mfaktc 0.20 and use GPU sieving. Depending on the exponent and bitlevel a GTX 670 should yield > 300M/s in best case (barrett76 kernel).
And you're right, for applications which make heavy use of integer instructions (like mfaktc), the newer chips are not so good. Anyway the energy efficiency (performance per watt while running mfaktc) is very good.

Oliver