mfaktc: a CUDA program for Mersenne prefactoring - Page 143

TheJudger · 2012-01-28, 17:49

firejuggler: yepp, I know (I receive automatic notices about new CUDA releases). You can expect new executables of mfaktc 0.18 using CUDA 4.1 soon.

MrRepunit: sorry, I haven't looked at your stuff yet.

Oliver

Dubslow · 2012-01-29, 05:28

Quote:

Originally Posted by Dubslow

Here's the issues I've had over the last 4 months or so with drivers.
http://forums.nvidia.com/index.php?showtopic=220802

AHAHAHHAHAHAHAHAHAHAHAA!!!

I finally got the damn drivers to install.

Code:

CUDA version info
  binary compiled for CUDA  4.0
  CUDA runtime version      4.10
  CUDA driver version       4.10

Please take your time TheJudger, I've been without my GPU for a few weeks due to driver issues, I can wait a few more days

TheJudger · 2012-01-29, 13:38

Hello!

http://www.mersenneforum.org/mfaktc/...win.cuda41.zip
http://www.mersenneforum.org/mfaktc/....cuda41.tar.gz

These executables are compiled with CUDA 4.1. The sourcecode is exactly the same than before so there is no need to repost the sourcecode. This version will use checkpoints from mfaktc 0.18 (CUDA 4.0)! CUDA 4.1 needs driver version 285 or newer.

If you're using a CC 1.x GPU than there is no need to update. If you're using a GPU with CC 2.0 this update is recommended (the GPU code just runs a little bit faster!). And those with CC 2.1 can try it, too, but I expect that the performance difference is barely noticeable.

Oliver

kladner · 2012-01-29, 18:42

-st2 completes without errors on a GTX 460 @ 875MHz, Win7-64 driver 290.53. I run the test on principle when there are any changes.

EDIT: Thanks for the updated version, Oliver.

oswald · 2012-01-29, 20:09

Most excellent! I have a GTX570 and it was doing about 500M/s. Now it is hitting 540M/s.

Thanks,
Roy

James Heinrich · 2012-01-29, 21:53

Quote:

Originally Posted by oswald

Most excellent! I have a GTX570 and it was doing about 500M/s. Now it is hitting 540M/s.

Just curious: with what SievePrimes and across how many instances? I ask because my GTX570 is doing around 400M/s at SP=5000, 2 instances, 71-72.

oswald · 2012-01-30, 00:39

5000 SievePrimes, six instances, from 68-78. I7/920 running at 2.67 Ghz.
Each instance eating 12% of CPU with 1% to 2% wait time.
NumStreams=8 and CPUStreams=3. Affinity is not set.
batch - cmd.exe /c "start "mfaktc 5" /low mfaktc-win-64.exe -v 2"
Windows 7 Ult.

If I use the computer and run prime95 with one worker window, it drops to about 480M/s to 500M/s.

GPU Load is 99%, Fan 86%, Temp 86C to 88C. Voltage 1.075V, Clock 911 Mhz, Memory 2106 Mhz and Shader 1822 Mhz.

James Heinrich · 2012-01-30, 02:09

Quote:

Originally Posted by oswald

5000 SievePrimes, six instances, from 68-78. I7/920 running at 2.67 Ghz.

How does your performance fare with 4 instances rather than 6? I suspect it wouldn't be much different, since you only have 4 cores to work with.

Also, on the topic that was raised before... any special reason you're taking these exponents abnormally high (to 2^78)?

oswald · 2012-01-30, 02:38

Six seems the fastest for me. Four and Five are a little slower, maybe 4% or 5%. Seven about the same, but more cpu time is wasted and Eight is slower with 100% cpu used.

I'm going to drop back to 72 when I'm done with the current 77 and a few 74s. I just wanted a couple to see if the program would process the larger bits faster or slower. I didn't see any difference.

Also I thought it would be cool. It wasn't.

flashjh · 2012-01-30, 03:03

Quote:

Originally Posted by oswald

Six seems the fastest for me. Four and Five are a little slower, maybe 4% or 5%. Seven about the same, but more cpu time is wasted and Eight is slower with 100% cpu used.

I'm going to drop back to 72 when I'm done with the current 77 and a few 74s. I just wanted a couple to see if the program would process the larger bits faster or slower. I didn't see any difference.

Also I thought it would be cool. It wasn't.

So, did you find any factors above 72?

oswald · 2012-01-30, 03:58

Quote:

Originally Posted by flashjh

So, did you find any factors above 72?

45385591,73

Just one. So it would seem that 72 is the sweet spot.

I've seen some TFs go by to 81. Anyone get any factors above 73?

2012-01-29, 13:38	#1565
TheJudger "Oliver" Mar 2005 Germany 11·101 Posts	mfaktc 0.18 - CUDA 4.1 Hello! http://www.mersenneforum.org/mfaktc/...win.cuda41.zip http://www.mersenneforum.org/mfaktc/....cuda41.tar.gz These executables are compiled with CUDA 4.1. The sourcecode is exactly the same than before so there is no need to repost the sourcecode. This version will use checkpoints from mfaktc 0.18 (CUDA 4.0)! CUDA 4.1 needs driver version 285 or newer. If you're using a CC 1.x GPU than there is no need to update. If you're using a GPU with CC 2.0 this update is recommended (the GPU code just runs a little bit faster!). And those with CC 2.1 can try it, too, but I expect that the performance difference is barely noticeable. Oliver

2012-01-29, 18:42	#1566
kladner "Kieren" Jul 2011 In My Own Galaxy! 23656₈ Posts	-st2 completes without errors on a GTX 460 @ 875MHz, Win7-64 driver 290.53. I run the test on principle when there are any changes. EDIT: Thanks for the updated version, Oliver. Last fiddled with by kladner on 2012-01-29 at 18:45

2012-01-30, 00:39	#1569
oswald Apr 2011 in vivo 3×5² Posts	5000 SievePrimes, six instances, from 68-78. I7/920 running at 2.67 Ghz. Each instance eating 12% of CPU with 1% to 2% wait time. NumStreams=8 and CPUStreams=3. Affinity is not set. batch - cmd.exe /c "start "mfaktc 5" /low mfaktc-win-64.exe -v 2" Windows 7 Ult. If I use the computer and run prime95 with one worker window, it drops to about 480M/s to 500M/s. GPU Load is 99%, Fan 86%, Temp 86C to 88C. Voltage 1.075V, Clock 911 Mhz, Memory 2106 Mhz and Shader 1822 Mhz. Last fiddled with by oswald on 2012-01-30 at 00:48

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
mfakto: an OpenCL program for Mersenne prefactoring	Bdot	GPU Computing	1676	2021-06-30 21:23
The P-1 factoring CUDA program	firejuggler	GPU Computing	753	2020-12-12 18:07
gr-mfaktc: a CUDA program for generalized repunits prefactoring	MrRepunit	GPU Computing	32	2020-11-11 19:56
mfaktc 0.21 - CUDA runtime wrong	keisentraut	Software	2	2020-08-18 07:03
World's second-dumbest CUDA program	fivemack	Programming	112	2015-02-12 22:51

2012-01-28, 17:49	#1563
TheJudger "Oliver" Mar 2005 Germany 1111₁₀ Posts	firejuggler: yepp, I know (I receive automatic notices about new CUDA releases). You can expect new executables of mfaktc 0.18 using CUDA 4.1 soon. MrRepunit: sorry, I haven't looked at your stuff yet. Oliver

2012-01-29, 20:09	#1567
oswald Apr 2011 in vivo 3·5² Posts	Most excellent! I have a GTX570 and it was doing about 500M/s. Now it is hitting 540M/s. Thanks, Roy

2012-01-30, 02:38	#1571
oswald Apr 2011 in vivo 113₈ Posts	Six seems the fastest for me. Four and Five are a little slower, maybe 4% or 5%. Seven about the same, but more cpu time is wasted and Eight is slower with 100% cpu used. I'm going to drop back to 72 when I'm done with the current 77 and a few 74s. I just wanted a couple to see if the program would process the larger bits faster or slower. I didn't see any difference. Also I thought it would be cool. It wasn't.