20210825, 13:26  #1 
"Ed Hall"
Dec 2009
Adirondack Mtns
2^{2}·7·197 Posts 
A few polyselect questions
I'm working on some scripts in which I'm doing the individual steps separately.
poly_deadline doesn't seem to be working for the individual steps even though it's listed correctly in the log. Does that only function when invoking the whole process? I'm seting up ranges for the coefficients and some ranges immediately end. Does this mean there is no appropriate leading coefficient for this range or does the program check a small number of random coefficients and then give up? I'm getting hundreds of thousands of np1 hits, listed in msieve.dat.m and therefore nps takes hours to complete, even if np1 only ran for a few minutes. Would the minimum e value setting do any good in limiting the hits in the first stage and if so, would I use the minimum Murphy_E or something else at this point? Thanks for any help. 
20210825, 16:04  #2 
Sep 2009
11×223 Posts 
poly_deadline=X is the number of CPU seconds that particular step should run for. I find it useful for GPU assisted searching, I do np1 and nps in parallel, using poly_deadline to make it stop after about 2% of estimated CPU time to do the whole job. But it's not much use if you don't know how many cores msieve will actually be using.
I then sort the stage 2 hits and put the top 100 or so through npr. I don't know any way to do that with stage 1 output since you don't have the escore at that point. Chris 
20210825, 16:09  #3 
"Vincent"
Apr 2010
Over the rainbow
2×3×5×97 Posts 
Run a few minute of np1 nps, then get the best escore... rerun with the new parameter. 
20210825, 16:31  #4  
"Ed Hall"
Dec 2009
Adirondack Mtns
158C_{16} Posts 
Quote:
Code:
Tue Aug 24 15:23:29 2021 poly select deadline: 300 Tue Aug 24 15:23:29 2021 time limit set to 0.08 CPUhours Additionally, I haven't had any success with getting more than one thread engaged. Will msieve poly selection use multithreading? I hadn't tried doing both steps at once. I'll "give it a go." 

20210825, 18:01  #5 
"Ed Hall"
Dec 2009
Adirondack Mtns
2^{2}·7·197 Posts 
Maybe this is why it doesn't stop at 300 seconds:
Code:
$ ../msieve t 12 np "poly_deadline=300 min_coeff=0 max_coeff=1000000 polydegree=6" deadline: 8640000 CPUseconds per coefficient coeff 120120 specialq 1  1030050632 other 484419  1162605 aprogs: 19335 entries, 75936 roots line minimize failed save 1.477489e16 8.5039 6685374.54 9.085104e17 rroots 4 Code:
Wed Aug 25 13:46:42 2021 poly select deadline: 300 Wed Aug 25 13:46:42 2021 time limit set to 0.08 CPUhours Edit: Also note that t 12 did nothing (as expected). Only one thread is running. Last fiddled with by EdH on 20210825 at 18:02 
20210825, 21:36  #6  
Jun 2012
3×1,327 Posts 
Quote:
Are you limiting the max_stage_1_norm (and 2)? With no limits (or bad limits) defined for these values you can collect a LOT of junk. 

20210826, 00:13  #7  
"Ed Hall"
Dec 2009
Adirondack Mtns
2^{2}·7·197 Posts 
Quote:
Code:
Wed Aug 25 13:46:42 2021 max stage 1 norm: 2.88e+28 Wed Aug 25 13:46:42 2021 max stage 2 norm: 1.12e+28 Edit: Where can I find what I should use for these options? Last fiddled with by EdH on 20210826 at 00:21 

20210826, 01:47  #8 
Jun 2012
3·1,327 Posts 
I use 5.5% of the stage1 default value, and 6% of the default stage2.
I find this gives good results with not too many polys to process. The msieve parser needs double quotes around all your arguments in the invocation line e.g. Code:
msieve v g 0 np1 nps “1,1000000 stage1_norm=[value1] stage2_norm=[value2]” s [output file name] Last fiddled with by swellman on 20210826 at 01:49 
20210826, 02:15  #9 
"Curtis"
Feb 2005
Riverside, CA
13242_{8} Posts 
I used to try to pick stage 1 norm tight enough to keep the nps part just able to keep up. I used "top" to judge this I wanted msieve to be near 100% cpu use, but not pinned at 100. This gave me some sense that sizeopt was keeping up with the output of the GPU.
I pick stage 2 norm to be default divided by 30, but that doesn't give many hits on smaller inputs; one might need a looser bound for regular use and a tighter bound for large (C170+) inputs. 
20210826, 11:30  #10 
Jun 2012
3·1,327 Posts 
Ed 
Just to add to the mix, I have some old notes: Poly search 5%12.5% of Stg1, 1%10% of a Stg2. 5.5%/6% seems best speed/yield mix. 3%/10% works 2x faster! (But it can miss good polys.) Note the above works for deg 5 but not really deg 6. Msieve doesn’t work great for larger GNFS, say in low 190s. I tend to use CADO for deg 6 or >C190. FWIW. 
20210826, 12:09  #11 
"Ed Hall"
Dec 2009
Adirondack Mtns
1010110001100_{2} Posts 
Thanks for all the help, everyone.
I still can't get poly_deadline to work, even though it says it's set in the log. As for the norms, I tried the 5.5/6% and ran a session overnight with 20 threads running different ranges. I hard stopped msieve at four hours, but that should have been roughly equal to 80 hours work. I woke this morning to an empty .ms file. Of note, msieve is defaulting to degree 5 for this 220 digit number, so I've been setting it to degree 6. Also, I haven't been able to get my arch 3.0 card to work with msieve (or GMPECM)* so I'm just running via CPUs ATM. *CUDA 10.X is supposed to support arch 3.0, but something causes a "trickle" of CUDA 11.X to sneak in. I guess the trouble was in my keeping up with the Ubuntu OSs. 
Thread Tools  
Similar Threads  
Thread  Thread Starter  Forum  Replies  Last Post 
Msieve failed to polyselect  firejuggler  Msieve  3  20181001 13:47 
Base method of montgomery polyselect implementation  csg  Homework Help  2  20171213 07:04 
Playing with CADO's individual polyselect binaries  Dubslow  CADONFS  22  20160704 19:54 
To CPU or to GPU: stage1 polyselect research  Karl M Johnson  Msieve  8  20111112 19:46 
Questions  joblack  Math  10  20090501 19:52 