[QUOTE=Sutton Shin;322807]Where is the program for windows 7 x64?[/QUOTE]mfaktc releases are archived here:
[url]http://www.mersenneforum.org/mfaktc/[/url]
You're looking for [b]mfaktc-0.19.win.cuda42.zip[/b]

I am going to edit the first post of the thread to put the link to /mfaktc into it, for who is coming next. Just FYI.

mfaktc win 0.19 cuda4.0
 

Hi,

I have an old cuda GPU (Quatro FX 880 M) with cuda 4.0. Only mfaktc 0.18 is compiled for cuda 4.0/4.1/4.2.

I saw that the new algo in 0.19 is almost +25% compare to v0.18.

Could someone compile mfaktc 0.19 for cuda 4.0 (on win) please?

Thanks,

Ludovic

[QUOTE=Aillas;323191]Could someone compile mfaktc 0.19 for cuda 4.0 (on win) please?[/QUOTE]v0.20 is getting very close to release (a few days, I believe), so you might even (soon) be able to get a CUDA 4.0 version of 0.20.
Be aware, however, that your GPU is CC v1.2 so all the benefits gained from GPU sieving in v0.20 won't be available to you, unfortunately.

Thanks for the info. waiting for the 0.20 :)

[QUOTE=James Heinrich;323193]v0.20 is getting very close to release (a few days, I believe), so you might even (soon) be able to get a CUDA 4.0 version of 0.20.
Be aware, however, that your GPU is CC v1.2 so all the benefits gained from GPU sieving in v0.20 won't be available to you, unfortunately.[/QUOTE]

I'm running the prerel version of 0.20 on the same FX 880M. I'm getting about 13.5 GHz-days/day (14.5 M/s, which is 0.5% more than v0.19 and about 20% more than v0.18).

Dumb question: will the GPU sieving in version 0.20 make multiple instances of mfaktc (for single GPUs) unnecessary?

[QUOTE=ixfd64;323577]Dumb question: will the GPU sieving in version 0.20 make multiple instances of mfaktc (for single GPUs) unnecessary?[/QUOTE]Yes, at least in my experience. A single GPU-sieving instance happily chews up an entire GTX 570. And gives about 400Ghd/d doing so, which is [I]considerably[/I] above my [URL="http://www.mersenne.ca/mfaktc.php"]benchmark charts[/URL] (which suggest around 255GHd/d) -- once v0.20 is released I'm going to request new benchmarks from everyone (but please wait until I've decided on test parameters).

Multiple GPUs (e.g. SLI) will still require one instance per GPU.

You can of course still run multiple instances on a single GPU if you like, and I've observed some interesting (to me) behavior in that it seemed to load-balance to give more GPU time to the harder assignments, if that makes any sense. For example, if you ran two instances on two 60M range exponents, one from 71-72 and one from 72-73, the latter takes twice the GHz-days to complete, but with GPU-sieving it seems that 72-73 gets double the GPU-time, so both assignments would complete in about the same real-time. I assume this is just an unintentional side-effect of the GPU sieving.

[QUOTE=James Heinrich;323607]Yes, at least in my experience. A single GPU-sieving instance happily chews up an entire GTX 570. And gives about 400Ghd/d doing so, which is [I]considerably[/I] above my [URL="http://www.mersenne.ca/mfaktc.php"]benchmark charts[/URL] (which suggest around 255GHd/d) -- once v0.20 is released I'm going to request new benchmarks from everyone (but please wait until I've decided on test parameters).

Multiple GPUs (e.g. SLI) will still require one instance per GPU.

You can of course still run multiple instances on a single GPU if you like, and I've observed some interesting (to me) behavior in that it seemed to load-balance to give more GPU time to the harder assignments, if that makes any sense. For example, if you ran two instances on two 60M range exponents, one from 71-72 and one from 72-73, the latter takes twice the GHz-days to complete, but with GPU-sieving it seems that 72-73 gets double the GPU-time, so both assignments would complete in about the same real-time. I assume this is just an unintentional side-effect of the GPU sieving.[/QUOTE]
I currently use 2 instances on my GTX 570M. I'll be happy to do some benchmarks for you if needed. I'll even deactivate prime95 during the benchmark (not the case right now).

[QUOTE=ixfd64;323577]Dumb question: will the GPU sieving in version 0.20 make multiple instances of mfaktc (for single GPUs) unnecessary?[/QUOTE]

Yes, as James allready told one instance per GPU is enough. And 32bit mfaktc is a little bit faster than 64bit mfaktc in case of GPU sieving. For CPU sieving the 64bit version is still recommended.

Oliver

[QUOTE=TheJudger;323674]And 32bit mfaktc is a little bit faster than 64bit mfaktc in case of GPU sieving. For CPU sieving the 64bit version is still recommended.[/QUOTE]That's interesting. Why the reversal?