The P-1 factoring CUDA program - Page 13

ET_ · 2013-04-26, 12:02

Quote:

Originally Posted by owftheevil

@ ET The timings are interesting, but the work on how big nrp can get without a crash is still just as important.

A recent run on a 570:

Selected B1=605000, B2=16637500, 4.1% chance of finding a factor
CUDA reports 732M of 1279M GPU memory free.
Using e=6, d=2310, nrp=10
Starting stage 1 P-1, M61410829, B1 = 605000, B2 = 16637500, e = 6, fft length = 3360K
.
.
.
Stage 1 complete, estimated total time = 1:41:14
.
.
.
Stage 2 complete, estimated total time = 3:42:23
M61410829 Stage 2 found no factor (P-1, B1=605000, B2=16637500, e=6, n=3360K CUDAPm1 v0.00)

There were ~350Mb of free memory during stage 2.

Should I continue the analysis?

Luigi

owftheevil · 2013-04-26, 13:00

Yes. Right now the memory settings are on the conservative side. Data from different cards about how much memory use they can tolerate would be very useful.

Edit: small b1 and small b2 or terminate after 1 pass of stage2, I just want to see if it handles the memory load.

ET_ · 2013-04-26, 13:28

Quote:

Originally Posted by owftheevil

Yes. Right now the memory settings are on the conservative side. Data from different cards about how much memory use they can tolerate would be very useful.

Edit: small b1 and small b2 or terminate after 1 pass of stage2, I just want to see if it handles the memory load.

Fine

Just one more question. The version I have can't be stopped during B2, while the one on sourceforge doesn't allow to modify the automatized parameters.

Or at least I didn't yet see how. :guilty:
I'll study during the weekend...

Luigi

owftheevil · 2013-04-26, 13:52

I just look up the process number and kill it.

ET_ · 2013-04-26, 14:12

Quote:

Originally Posted by owftheevil

I just look up the process number and kill it.

That way you don't have the presumed time to complete Stage 2...

But will be waaaaay faster

Luigi

frmky · 2013-04-28, 01:46

Quote:

Originally Posted by owftheevil

There were ~350Mb of free memory during stage 2.

The current version now reports expected memory use. Please compare that to the amount of memory used as reported by the driver to see if it is reasonably accurate. It looks accurate on both my K20 and GTX 480. There is additional memory free as reported by the driver, but CUDA says it isn't free and I'm going with what CUDA reports.

nucleon · 2013-05-01, 11:36

I'll add a me too.

When the windows exe gets released, I have a Titan here itching to have a bash at P-1.

-- Craig

frmky · 2013-05-02, 06:07

Here's a Windows version to try:
https://www.dropbox.com/s/hdu6eqwkk9...1_20130501.zip

Included is a worktodo.txt that should find a factor. I can't actually test it here since I have no Windows machine with a CC >= 1.3 card, so please try that first, make sure the factor is found, and please let me know if it worked!

There is a problem with reading the text entries in the .ini file, but the numerical entries work fine. Something in parse.c that Visual Studio doesn't like, but I don't have the motivation to track that down right now. It just uses the default input and output files, worktodo.txt and results.txt.

Also, make sure you have the latest graphics drivers. I compiled with CUDA 5.0 downloaded today.

firejuggler · 2013-05-02, 08:47

looking good for now

Code:

C:\Users\Vincent\Desktop\cudapm1>CUDAPm1.exe

Warning: Couldn't parse ini file option WorkFile; using default "worktodo.txt"
Warning: Couldn't parse ini file option ResultsFile; using default "results.txt"

Selected B1=605000, B2=16637500, 4.1% chance of finding a factor
CUDA reports zuM of zuM GPU memory free.
Using e=2, d=210, nrp=4
Using approximately zuM GPU memory.
Starting stage 1 P-1, M61262347, B1 = 605000, B2 = 16637500, e = 2, fft length =
 3360K
Doing 873133 iterations
Iteration 1000 M61262347, 0xf19a7f6041953a97, n = 3360K, CUDAPm1 v0.00 err = 0.2
1094 (0:16 real, 16.1885 ms/iter, ETA 3:55:18)
Iteration 2000 M61262347, 0xaf1d15aad49fcee8, n = 3360K, CUDAPm1 v0.00 err = 0.1
9336 (0:13 real, 12.8097 ms/iter, ETA 3:05:58)
Iteration 3000 M61262347, 0xb702298e7a8c9a8e, n = 3360K, CUDAPm1 v0.00 err = 0.2
1680 (0:13 real, 12.8040 ms/iter, ETA 3:05:41)
Iteration 4000 M61262347, 0xc53d1695707d3dc0, n = 3360K, CUDAPm1 v0.00 err = 0.1
9922 (0:13 real, 12.7794 ms/iter, ETA 3:05:07)
Iteration 5000 M61262347, 0xf154bc3c5f15a9c9, n = 3360K, CUDAPm1 v0.00 err = 0.1
9727 (0:12 real, 12.8228 ms/iter, ETA 3:05:31)

Will report back tonight

Stef42 · 2013-05-02, 09:37

I got it running in Windows 8, but it crashed when starting stage 2.

Code:

Stage 1 complete, estimated total time = 1:20:10
Starting stage 1 gcd.
M61262347 Stage 1 found no factor (P-1, B1=605000, B2=16637500, e=6, n=3360K CUDAPm1 v0.00
Starting stage 2

Some details:
memusage during stage 1: 334MB (MSI afterburner)
memusage during start of stage 2: 1185MB

Total video memory is 1,5GB. I'm trying to figure out if there was not enough memory for some reason.
Details of my graphics card: http://www.msi.com/product/vga/N580GTX-Lightning.html

owftheevil · 2013-05-02, 11:59

If its not able to allocate the stage 2 memory, it should be giving you a message like this:

Code:

CUDAPm1.cu(2628) : cudaSafeCall() Runtime API error 2: out of memory.

So something else is likely going on.

Also, the difference in memory use between stage 1 and the beginning of stage 2 is consistent with e = 6 and nrp = 24. Is that what you saw?

2013-04-26, 13:00	#134
owftheevil "Carl Darby" Oct 2012 Spring Mountains, Nevada 3²·5·7 Posts	Yes. Right now the memory settings are on the conservative side. Data from different cards about how much memory use they can tolerate would be very useful. Edit: small b1 and small b2 or terminate after 1 pass of stage2, I just want to see if it handles the memory load. Last fiddled with by owftheevil on 2013-04-26 at 13:05

2013-05-02, 09:37	#142
Stef42 Feb 2012 the Netherlands 2·29 Posts	I got it running in Windows 8, but it crashed when starting stage 2. Code: Stage 1 complete, estimated total time = 1:20:10 Starting stage 1 gcd. M61262347 Stage 1 found no factor (P-1, B1=605000, B2=16637500, e=6, n=3360K CUDAPm1 v0.00 Starting stage 2 Some details: memusage during stage 1: 334MB (MSI afterburner) memusage during start of stage 2: 1185MB Total video memory is 1,5GB. I'm trying to figure out if there was not enough memory for some reason. Details of my graphics card: http://www.msi.com/product/vga/N580GTX-Lightning.html

2013-05-02, 11:59	#143
owftheevil "Carl Darby" Oct 2012 Spring Mountains, Nevada 473₈ Posts	If its not able to allocate the stage 2 memory, it should be giving you a message like this: Code: CUDAPm1.cu(2628) : cudaSafeCall() Runtime API error 2: out of memory. So something else is likely going on. Also, the difference in memory use between stage 1 and the beginning of stage 2 is consistent with e = 6 and nrp = 24. Is that what you saw? Last fiddled with by owftheevil on 2013-05-02 at 12:05

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
mfaktc: a CUDA program for Mersenne prefactoring	TheJudger	GPU Computing	3497	2021-06-05 12:27
World's second-dumbest CUDA program	fivemack	Programming	112	2015-02-12 22:51
World's dumbest CUDA program?	xilman	Programming	1	2009-11-16 10:26
Factoring program need help	Citrix	Lone Mersenne Hunters	8	2005-09-16 02:31
Factoring program	ET_	Programming	3	2003-11-25 02:57

2013-04-26, 13:52	#136
owftheevil "Carl Darby" Oct 2012 Spring Mountains, Nevada 3²×5×7 Posts	I just look up the process number and kill it.

2013-05-01, 11:36	#139
nucleon Mar 2003 Melbourne 1003₈ Posts	I'll add a me too. When the windows exe gets released, I have a Titan here itching to have a bash at P-1. -- Craig

2013-05-02, 06:07	#140
frmky Jul 2003 So Cal 2²·23² Posts	Here's a Windows version to try: https://www.dropbox.com/s/hdu6eqwkk9...1_20130501.zip Included is a worktodo.txt that should find a factor. I can't actually test it here since I have no Windows machine with a CC >= 1.3 card, so please try that first, make sure the factor is found, and please let me know if it worked! There is a problem with reading the text entries in the .ini file, but the numerical entries work fine. Something in parse.c that Visual Studio doesn't like, but I don't have the motivation to track that down right now. It just uses the default input and output files, worktodo.txt and results.txt. Also, make sure you have the latest graphics drivers. I compiled with CUDA 5.0 downloaded today.