mfaktc: a CUDA program for Mersenne prefactoring - Page 84

drh · 2011-05-14, 11:22

I've tried quite a few times to upload it again, with no success.

When I upload the file, the screen just sits there until I get a partial screen returned, like it times out. Everything else seems to working fine, other than the database not being available off and on this morning.

axn · 2011-05-14, 11:28

Quote:

Originally Posted by drh

I've tried quite a few times to upload it again, with no success.

When I upload the file, the screen just sits there until I get a partial screen returned, like it times out. Everything else seems to working fine, other than the database not being available off and on this morning.

Don't upload the whole file again & again!! Just copy the single line and paste it into the manual upload form

drh · 2011-05-14, 11:31

Quote:

Originally Posted by axn

Don't upload the whole file again & again!! Just copy the single line and paste it into the manual upload form

After the first upload, I deleted all the other lines, so I was left with only the two lines related to the factor ...

M76120789 has a factor: 5666251615825315865351
found 1 factor(s) for M76120789 from 2^72 to 2^73 [mfaktc 0.16p1-Win barrett79_mul32]

I'll try to cut and paste it into the form and see if that works.

drh · 2011-05-14, 11:40

Quote:

Originally Posted by drh

After the first upload, I deleted all the other lines, so I was left with only the two lines related to the factor ...

M76120789 has a factor: 5666251615825315865351
found 1 factor(s) for M76120789 from 2^72 to 2^73 [mfaktc 0.16p1-Win barrett79_mul32]

I'll try to cut and paste it into the form and see if that works.

Still no luck using the form ... same result, partial screen returned.

axn · 2011-05-14, 11:49

Quote:

Originally Posted by drh

Still no luck using the form ... same result, partial screen returned.

Hmmm... Apparently, the issue is at the server itself. I guess you'll have to wait till it is up & running again. See: http://www.mersenneforum.org/showthread.php?t=15602

drh · 2011-05-14, 11:52

Quote:

Originally Posted by axn

Hmmm... Apparently, the issue is at the server itself. I guess you'll have to wait till it is up & running again. See: http://www.mersenneforum.org/showthread.php?t=15602

I'll try it once in a while throughout the day.

Thanks,
Doug

nucleon · 2011-05-14, 12:18

http://mersenneforum.org/showpost.ph...09&postcount=3

nucleon · 2011-05-15, 01:40

Quote:

Originally Posted by axn

Hmmm... Apparently, the issue is at the server itself. I guess you'll have to wait till it is up & running again. See: http://www.mersenneforum.org/showthread.php?t=15602

Yep, there's definitely an issue with submission of factor results. No factor results work perfectly.

I have now 2x factor results ready for submission when it gets back. I guess we'll have to wait until the server admins get a chance to look at it.

-- Craig

Christenson · 2011-05-18, 00:40

The server issue is now fixed...exact cause unspecified.....

Christenson · 2011-05-18, 02:23

Got to thinking about how to structure the mfaktc interaction with primenet tonight, looking at how my "results.txt" gets hand marked-up about what's been reported or not.

The conclusion is that the output side should be a queue -- basically, a machine-edited version of what is in results.txt (call it results.queue) that the primenet thread/task looks at to decide what to tell the server, and deletes the front of when it is done. This allows mfaktc to be stopped and started as needed. I'm sure Prime95 can tell me how big the largest exponent I can report on is, so anything done for Operation Billion Digits can be dropped and reported manually. In addition, when the primenet task succeeds in reporting a result, it writes a line about the success to results.txt, unless a key tells it not to. Finally, this is in addition to any sort of log that the primenet task might create detailing all of its travails.

This has the huge advantage of de-coupling the problem of input from the problem of output.

TheJudger · 2011-05-18, 08:52

Quote:

Originally Posted by Christenson

Got to thinking about how to structure the mfaktc interaction with primenet tonight, looking at how my "results.txt" gets hand marked-up about what's been reported or not.

The conclusion is that the output side should be a queue -- basically, a machine-edited version of what is in results.txt (call it results.queue) that the primenet thread/task looks at to decide what to tell the server, and deletes the front of when it is done. This allows mfaktc to be stopped and started as needed. I'm sure Prime95 can tell me how big the largest exponent I can report on is, so anything done for Operation Billion Digits can be dropped and reported manually. In addition, when the primenet task succeeds in reporting a result, it writes a line about the success to results.txt, unless a key tells it not to. Finally, this is in addition to any sort of log that the primenet task might create detailing all of its travails.

This has the huge advantage of de-coupling the problem of input from the problem of output.

Prime95 uses a "prime.spl" (spool file) for the results. This file should (must) be secured against modifications.
Human readable results.txt and machine readable spool file is a good idea. For mfaktc one idea would be a function which adds a result to the spool file with some additional data if the result was the last one (last bit level) or not for the specified exponent. If it is the last result it is save to sent the result.

Oliver

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

2011-05-14, 11:22	#914
drh Jan 2011 Cincinnati, OH 2²·5² Posts	I've tried quite a few times to upload it again, with no success. When I upload the file, the screen just sits there until I get a partial screen returned, like it times out. Everything else seems to working fine, other than the database not being available off and on this morning.

2011-05-14, 12:18	#920
nucleon Mar 2003 Melbourne 1003₈ Posts	http://mersenneforum.org/showpost.ph...09&postcount=3

2011-05-18, 00:40	#922
Christenson Dec 2010 Monticello 5·359 Posts	The server issue is now fixed...exact cause unspecified.....

2011-05-18, 02:23	#923
Christenson Dec 2010 Monticello 5·359 Posts	Got to thinking about how to structure the mfaktc interaction with primenet tonight, looking at how my "results.txt" gets hand marked-up about what's been reported or not. The conclusion is that the output side should be a queue -- basically, a machine-edited version of what is in results.txt (call it results.queue) that the primenet thread/task looks at to decide what to tell the server, and deletes the front of when it is done. This allows mfaktc to be stopped and started as needed. I'm sure Prime95 can tell me how big the largest exponent I can report on is, so anything done for Operation Billion Digits can be dropped and reported manually. In addition, when the primenet task succeeds in reporting a result, it writes a line about the success to results.txt, unless a key tells it not to. Finally, this is in addition to any sort of log that the primenet task might create detailing all of its travails. This has the huge advantage of de-coupling the problem of input from the problem of output.