The P-1 factoring CUDA program - Page 16

kracker · 2013-05-02, 19:13

Quote:

Originally Posted by c10ck3r

Q? about proto-p-1-cuda...
Is the does it write a .bu or .bu2 file like P95 does? If so, are they compatible? i.e. could I run Stage 1 on GPU and Stage 2 on CPU?

I believe I read your answer is somewhere in this thread.

EDIT: Or maybe that was on CuLu, I can't remember. :(

owftheevil · 2013-05-02, 19:18

About the 1000000009 run, I got to thinking (funny how I do most of that after speaking) that you would need an incredible amount of memory to get that to work, ~4.2GB at the absolute minimum. ~2.4 just for stage 1.

James Heinrich · 2013-05-02, 19:23

Far beyond my card, but Karl mentioned above he has a 6GB vidcard...

kracker · 2013-05-02, 19:35

Quote:

Originally Posted by James Heinrich

Far beyond my card, but Karl mentioned above he has a 6GB vidcard...

The Titan is the only nVidia Geforce card I think that has 6 GB.

EDIT: That or the Tesla K20X...

firejuggler · 2013-05-02, 20:29

there.
window7 home premium (64 bit)

Code:

Iteration 873000 M61262347, 0x92b46441f57f0dc1, n = 3360K, CUDAPm1 v0.00 err = 0
.19531 (0:13 real, 12.7994 ms/iter, ETA 0:01)
M61262347, 0xfd7ab9d857ea4a36, offset = 0, n = 3360K, CUDAPm1 v0.00
Stage 1 complete, estimated total time = 3:06:32
Starting stage 1 gcd.
M61262347 Stage 1 found no factor (P-1, B1=605000, B2=16637500, e=2, n=3360K CUD
APm1 v0.00)
Starting stage 2.
Zeros: 875508, Ones: 853116, Pairs: 166845
itime: 1.982408, transforms: 1, average: 1982.408000
ptime: 1863.879498, transforms: 285724, average: 6.523356
ETA: 5:42:04
itime: 2.236556, transforms: 1, average: 2236.556000
ptime: 1867.422307, transforms: 286126, average: 6.526573
ETA: 5:11:17
itime: 2.341590, transforms: 1, average: 2341.590000
ptime: 1863.484573, transforms: 286070, average: 6.514086
ETA: 4:40:04
itime: 2.443132, transforms: 1, average: 2443.132000
ptime: 1864.386307, transforms: 286206, average: 6.514141
ETA: 4:08:56
itime: 2.479896, transforms: 1, average: 2479.896000
ptime: 1865.738907, transforms: 286420, average: 6.513997
ETA: 3:37:50
itime: 2.566038, transforms: 1, average: 2566.038000
ptime: 1866.830105, transforms: 286588, average: 6.513986
ETA: 3:06:45
itime: 2.578672, transforms: 1, average: 2578.672000
ptime: 1863.986985, transforms: 286146, average: 6.514112
ETA: 2:35:37
itime: 2.578564, transforms: 1, average: 2578.564000
ptime: 1868.104663, transforms: 286782, average: 6.514023
ETA: 2:04:31
itime: 2.616162, transforms: 1, average: 2616.162000
ptime: 1864.357941, transforms: 286198, average: 6.514224
ETA: 1:33:23
itime: 2.704018, transforms: 1, average: 2704.018000
ptime: 1869.413957, transforms: 286978, average: 6.514137
ETA: 1:02:16
itime: 2.703811, transforms: 1, average: 2703.811000
ptime: 1861.521090, transforms: 285758, average: 6.514327
ETA: 31:07
itime: 2.665333, transforms: 1, average: 2665.333000
ptime: 1862.245724, transforms: 285860, average: 6.514538
ETA: 0:00
Stage 2 complete, estimated total time = 6:13:31
Accumulated Product: M61262347, 0xa77ba20d6e2648c2, n = 3360K, CUDAPm1 v0.00
Starting stage 2 gcd.
M61262347 has a factor: 195362848474407049033033 (P-1, B1=605000, B2=16637500, e
=2, n=3360K CUDAPm1 v0.00)

Cudaluca 5.0 installed too. on a gtx560, 1024 Mo ram.

firejuggler · 2013-05-02, 20:49

now thanks to jwb52z we have

Code:

P-1 found a factor in stage #1, B1=580000.
UID: Jwb52z/Clay, M61761811 has a factor: 664146289430268916763473

79.136 bits.

wich is k = 2^3 * 3 * 269 * 331 * 8363 * 300857
wich coulld tehorically found with a B1 of 8363 and a B2 of 300857.
stage 1 used 355 Mb of ram and stage 2 838
and 850 with stage2 GCD

Code:

C:\Users\Vincent\Desktop\cudapm1>CUDAPm1.exe 61761811 -b1 8363 -b2 300857

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

CUDA reports zuM of zuM GPU memory free.
Using e=2, d=210, nrp=6
Using approximately zuM GPU memory.
Starting stage 1 P-1, M61761811, B1 = 8363, B2 = 300857, e = 2, fft length = 336
0K
Doing 12072 iterations
Iteration 1000 M61761811, 0x58d24f1daf85c89d, n = 3360K, CUDAPm1 v0.00 err = 0.2
2656 (0:16 real, 16.2453 ms/iter, ETA 2:59)
Iteration 2000 M61761811, 0xbf2f93dbb5319ece, n = 3360K, CUDAPm1 v0.00 err = 0.2
4219 (0:13 real, 12.9319 ms/iter, ETA 2:10)
Iteration 3000 M61761811, 0x92d6f0e4c26aff33, n = 3360K, CUDAPm1 v0.00 err = 0.2
3438 (0:13 real, 12.8572 ms/iter, ETA 1:56)

...

22656 (0:13 real, 12.8680 ms/iter, ETA 0:13)
Iteration 12000 M61761811, 0x19f76d7f61bb24ed, n = 3360K, CUDAPm1 v0.00 err = 0.
23828 (0:13 real, 12.9096 ms/iter, ETA 0:00)
M61761811, 0xd041eb56158c648e, offset = 0, n = 3360K, CUDAPm1 v0.00
Stage 1 complete, estimated total time = 2:39
Starting stage 1 gcd.
M61761811 Stage 1 found no factor (P-1, B1=8363, B2=300857, e=2, n=3360K CUDAPm1
 v0.00)
Starting stage 2.
Zeros: 11856, Ones: 19440, Pairs: 5592
itime: 2.051921, transforms: 1, average: 2051.921000
ptime: 48.817234, transforms: 7426, average: 6.573826
ETA: 5:56
iETA: 0:51
itime: 2.995641, transforms: 1, average: 2995.641000
ptime: 49.863910, transforms: 7440, average: 6.702138
ETA: 0:00
Stage 2 complete, estimated total time = 6:56
Accumulated Product: M61761811, 0x5e6c85d01c0aae6e, n = 3360K, CUDAPm1 v0.00
Starting stage 2 gcd.
M61761811 has a factor: 664146289430268916763473 (P-1, B1=8363, B2=300857, e=2,
n=3360K CUDAPm1 v0.00)

Karl M Johnson · 2013-05-02, 21:51

Technically, with that binary, we should not be able to use more than 2GB of vRAM and 3-4GB of RAM, for it is 32 bit

This should be worth mentioning.

firejuggler · 2013-05-02, 22:16

another thing :

Code:

M55824233 has a factor: 833043841114609831879 (P-1, B1=839, B2=11550, e=2, n=307
2K CUDAPm1 v0.00)

This one has a k of p1*p2*...*839 aand should have been found with a B1 of 839. it doesn't find it. I have to wait till the end of stage 2 to get the factor.

owftheevil · 2013-05-02, 23:05

One problem fixed.

Code:

filbert@filbert:~/Build/cudapm1-0.00/cudapm1-code/trunk$ ./CUDAPm1 55824233 -b1 839

CUDA reports 716M of 1279M GPU memory free.
Using e=6, d=2310, nrp=12
Using approximately 681M GPU memory.
B1 should be at least 18324, increasing it.
Starting stage 1 P-1, M55824233, B1 = 839, B2 = 12625000, e = 6, fft length = 3072K
Doing 1239 iterations
Iteration 1000 M55824233, 0xa6b0b535ca74136a, n = 3072K, CUDAPm1 v0.00 err = 0.16406 (0:16 real, 15.6659 ms/iter, ETA 0:03)
M55824233, 0x8e2dd418ceb91638, offset = 0, n = 3072K, CUDAPm1 v0.00
Stage 1 complete, estimated total time = 0:18
Starting stage 1 gcd.
M55824233 has a factor: 833043841114609831879 (P-1, B1=839, B2=12625000, e=6, n=3072K CUDAPm1 v0.00)

firejuggler · 2013-05-02, 23:42

Thanks. I guess that was an easy one.

Aramis Wyler · 2013-05-02, 23:59

Will there be a new windows build with the stage1 fix in? I have an unusual 580 that I would be willing to run some tests against.

2013-05-02, 19:18	#167
owftheevil "Carl Darby" Oct 2012 Spring Mountains, Nevada 3²×5×7 Posts	About the 1000000009 run, I got to thinking (funny how I do most of that after speaking) that you would need an incredible amount of memory to get that to work, ~4.2GB at the absolute minimum. ~2.4 just for stage 1. Last fiddled with by owftheevil on 2013-05-02 at 19:20

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-05-02, 19:23	#168
James Heinrich "James Heinrich" May 2004 ex-Northern Ontario D5D₁₆ Posts	Far beyond my card, but Karl mentioned above he has a 6GB vidcard...

2013-05-02, 21:51	#172
Karl M Johnson Mar 2010 3×137 Posts	Technically, with that binary, we should not be able to use more than 2GB of vRAM and 3-4GB of RAM, for it is 32 bit This should be worth mentioning.

2013-05-02, 22:16	#173
firejuggler Apr 2010 Over the rainbow 2606₁₀ Posts	another thing : Code: M55824233 has a factor: 833043841114609831879 (P-1, B1=839, B2=11550, e=2, n=307 2K CUDAPm1 v0.00) This one has a k of p1p2...*839 aand should have been found with a B1 of 839. it doesn't find it. I have to wait till the end of stage 2 to get the factor.

2013-05-02, 23:42	#175
firejuggler Apr 2010 Over the rainbow 2×1,303 Posts	Thanks. I guess that was an easy one.

2013-05-02, 23:59	#176
Aramis Wyler "Bill Staffen" Jan 2013 Pittsburgh, PA, USA 2³·53 Posts	Will there be a new windows build with the stage1 fix in? I have an unusual 580 that I would be willing to run some tests against.