The P-1 factoring CUDA program - Page 69

aaronhaviland · 2019-11-23, 16:36

*tap*tap* is this thing still on?

I freed up some time from other hobbies recently, and am thinking about getting back involved with this. It'll take me a while to get my devel environment back up to speed, but I figured I'd throw this out there if there's any interest.

Of note, I'm completely out of touch with the current state of all things factoring related, so if there's anything I should be aware of before I dive back in, please let me know!

Thanks, and happy factoring :)

(On a side note: I think my GPU is dying. I only get reliable results if I underclock it. This is sad for me, but it also gives me a reliable source of hardware errors to test with that I hadn't had before, so who knows, maybe it can help me make things more robust.)

storm5510 · 2020-09-08, 12:28

Quote:

Originally Posted by aaronhaviland

*tap*tap* is this thing still on?

*Tap *tap... Nope. It's dead.

James Heinrich · 2020-09-08, 12:34

Quote:

Originally Posted by storm5510

*Tap *tap... Nope. It's dead.

But gpuowl is very much alive, and the current go-to program for all non-TF GPU worktypes, other than TF for which stick with mfaktc/mfakto.

storm5510 · 2020-09-08, 15:36

Quote:

Originally Posted by James Heinrich

But gpuowl is very much alive, and the current go-to program for all non-TF GPU worktypes, other than TF for which stick with mfaktc/mfakto.

I meant to add that. Sorry!

kriesel · 2020-09-08, 16:15

There are some NVIDIA gpus which can not run gpuowl, but can run cudapm1 or CUDALucas. They tend to be limited by gpu ram, and by cudapm1 issues. See https://www.mersenneforum.org/showthread.php?t=23389.

Addition of the Jacobi check to CUDALucas would be a big plus, and likely to be useful in confirming the next Mersenne prime discovery.

Implementing error checks in P-1 (either gpuowl or CUDAPm1 or anything else) is more complicated, and also needed. (In the LL series, the correct Jacobi symbol is known. In P-1 computations, it must be both calculated and checked.) See also https://www.mersenneforum.org/showthread.php?t=24168 for some ideas, particularly https://www.mersenneforum.org/showpo...1&postcount=10

But yeah, no reply in the thread for about 10 months, means it might have already missed Aaron Haviland's window of availability.

Dylan14 · 2020-12-12, 18:07

I have made a PKGBUILD for this software. You can find it here: https://aur.archlinux.org/packages/cudapm1/.

Also, attached is a CUDA 11.1 Linux build of cudapm1, compiled on an Arch Linux system with a GTX 1660 ti.

2020-09-08, 16:15	#753
kriesel "TF79LL86GIMPS96gpu17" Mar 2017 US midwest 17×433 Posts	There are some NVIDIA gpus which can not run gpuowl, but can run cudapm1 or CUDALucas. They tend to be limited by gpu ram, and by cudapm1 issues. See https://www.mersenneforum.org/showthread.php?t=23389. Addition of the Jacobi check to CUDALucas would be a big plus, and likely to be useful in confirming the next Mersenne prime discovery. Implementing error checks in P-1 (either gpuowl or CUDAPm1 or anything else) is more complicated, and also needed. (In the LL series, the correct Jacobi symbol is known. In P-1 computations, it must be both calculated and checked.) See also https://www.mersenneforum.org/showthread.php?t=24168 for some ideas, particularly https://www.mersenneforum.org/showpo...1&postcount=10 But yeah, no reply in the thread for about 10 months, means it might have already missed Aaron Haviland's window of availability. Last fiddled with by kriesel on 2020-09-08 at 16:34

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
mfaktc: a CUDA program for Mersenne prefactoring	TheJudger	GPU Computing	3622	2023-01-25 16:41
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

2019-11-23, 16:36	#749
aaronhaviland Jan 2011 Dudley, MA, USA 73 Posts	taptap* is this thing still on? I freed up some time from other hobbies recently, and am thinking about getting back involved with this. It'll take me a while to get my devel environment back up to speed, but I figured I'd throw this out there if there's any interest. Of note, I'm completely out of touch with the current state of all things factoring related, so if there's anything I should be aware of before I dive back in, please let me know! Thanks, and happy factoring :) (On a side note: I think my GPU is dying. I only get reliable results if I underclock it. This is sad for me, but it also gives me a reliable source of hardware errors to test with that I hadn't had before, so who knows, maybe it can help me make things more robust.)