Which poly to use? - Page 2

Karl M Johnson · 2010-06-01, 19:15

Henry, I've disabled UAC long ago.So all apps run as admin by default.
The def-par.txt file isnt present, but I dont know how should it look like!

henryzz · 2010-06-01, 19:20

Quote:

Originally Posted by Karl M Johnson

Henry, I've disabled UAC long ago.So all apps run as admin by default.
The def-par.txt file isnt present, but I dont know how should it look like!

try this
http://ggnfs.svn.sourceforge.net/vie...in/def-par.txt

Karl M Johnson · 2010-06-01, 19:33

Good gravy, it works! Thanks!

Karl M Johnson · 2010-06-01, 21:11

Factoring RSA-100 with FactMsieve.py script took 3816 seconds(that's excluding Polynomial selection).

Now, when running Poly for RSA-110, I've noticed something really interesting in Msieve.
An easter egg from Jason?

Mini-Geek · 2010-06-01, 21:34

Quote:

Originally Posted by Karl M Johnson

Factoring RSA-100 with FactMsieve.py script took 3816 seconds(that's excluding Polynomial selection).

Now, when running Poly for RSA-110, I've noticed something really interesting in Msieve.
An easter egg from Jason?

More likely a debugging result that's printed when an inconsequential bug happens, that shouldn't really have been included in the publicly-released version.

Karl M Johnson · 2010-06-01, 22:01

A little offtop, but is it possible to override time limit for poly selection for GPU aware Msieve?Didnt find the parameter.
If not, I think this will be a good addition.

fivemack · 2010-06-01, 22:31

You can effectively override the time limit by defining the search region explicitly using -np 1,1000 or similar, though you have to run -np 1,1000 to see how long that takes before running -np 1001,X for X large enough to take the amount of time you want.

Though I usually use this when searching on several CPUs; I have only one decent GPU to use.

jasonp · 2010-06-02, 01:41

That bug used to crop up a lot more often, and seeing it led to important fixes. They're not gone yet, and someday I'll have the time to get rid of the last debugging messages.

Karl M Johnson · 2010-06-02, 05:44

I'm using GTX 285 for Polynomial selection.
Running msieve with -np X,Y still results in the following string in logfile

Code:

time limit set to 0.97 hours

Guess it's coded and cant be overridden.

jrk · 2010-06-02, 06:07

Quote:

Originally Posted by Karl M Johnson

I'm using GTX 285 for Polynomial selection.
Running msieve with -np X,Y still results in the following string in logfile

Code:

time limit set to 0.97 hours

Guess it's coded and cant be overridden.

It prints that message but the time limit is ignored. I'll get around to patching it to suppress the message in awhile.

jrk · 2010-06-02, 06:30

Quote:

Originally Posted by jrk

It prints that message but the time limit is ignored. I'll get around to patching it to suppress the message in awhile.

fixed in svn 289

2010-06-01, 22:01	#17
Karl M Johnson Mar 2010 3×137 Posts	A little offtop, but is it possible to override time limit for poly selection for GPU aware Msieve?Didnt find the parameter. If not, I think this will be a good addition. Last fiddled with by Karl M Johnson on 2010-06-01 at 22:04

2010-06-02, 05:44	#20
Karl M Johnson Mar 2010 3·137 Posts	I'm using GTX 285 for Polynomial selection. Running msieve with -np X,Y still results in the following string in logfile Code: time limit set to 0.97 hours Guess it's coded and cant be overridden.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Poly search candidates	schickel	Msieve	32	2013-11-05 19:11
Good enough poly for c155?	theuser	Msieve	4	2012-10-07 09:00
GNFS poly selection	frmky	Factoring	14	2012-07-23 01:57
Can someone run a couple of poly searches for me?	schickel	Msieve	12	2012-05-25 03:45
poly selection in MPQS	bsquared	Factoring	3	2007-02-28 14:22

2010-06-01, 19:15	#12
Karl M Johnson Mar 2010 19B₁₆ Posts	Henry, I've disabled UAC long ago.So all apps run as admin by default. The def-par.txt file isnt present, but I dont know how should it look like!

2010-06-01, 19:33	#14
Karl M Johnson Mar 2010 110011011₂ Posts	Good gravy, it works! Thanks!

2010-06-01, 21:11	#15
Karl M Johnson Mar 2010 3·137 Posts	Factoring RSA-100 with FactMsieve.py script took 3816 seconds(that's excluding Polynomial selection). Now, when running Poly for RSA-110, I've noticed something really interesting in Msieve. An easter egg from Jason?

2010-06-01, 22:31	#18
fivemack (loop (#_fork)) Feb 2006 Cambridge, England 6419₁₀ Posts	You can effectively override the time limit by defining the search region explicitly using -np 1,1000 or similar, though you have to run -np 1,1000 to see how long that takes before running -np 1001,X for X large enough to take the amount of time you want. Though I usually use this when searching on several CPUs; I have only one decent GPU to use.

2010-06-02, 01:41	#19
jasonp Tribal Bullet Oct 2004 3,541 Posts	That bug used to crop up a lot more often, and seeing it led to important fixes. They're not gone yet, and someday I'll have the time to get rid of the last debugging messages.