20220524, 17:26  #67  
Jun 2012
2^{6}·59 Posts 
Quote:
Another strategy you could try is running this job on 15e_small with all its constraints and then sieve locally until you can get the job into LA. 

20220524, 18:04  #68 
"Curtis"
Feb 2005
Riverside, CA
2×7×397 Posts 
3 large prime jobs produce matrices 1020% larger than jobs with 2LP on both sides, when comparing the samesize job (both SNFS and GNFS). I usually go for 510% more raw relations when stepping from 2LP on both sides to 3LP on one side, to try to mitigate this. For me, when testsieving I want to see 3LP at least 10% faster than 2LP to make up for these effects.
Larger lims do make a larger matrix, but I haven't noticed any obvious scaling to advise, such as 200/200 lim's making a 5% larger matrix than 134/134. I can say the effect must not be too big, else the effect would stick out more clearly in our data maybe 5% or less. If 3LP is on the sieve side, keeping sieveside lim at 134M and pushing the other side to 266M maximizes the yield possible under Greg's "lims add to 400M" guidance, a rule that caps memory use of each siever process. Another trick that adds yield without (notably) larger matrix is to add an LP to the 2LP side, 32/33 instead of 32/32. I've run a bunch of jobs with 33/64 or 33/65 on the nonsieveside, and required number of relations to get the samesize matrix as a 32/32 job only rises by 3035%; I usually find yield goes up by more than 35%, so it seems a clear win. EDIT: I didn't quite answer all your questions. Sieve range is an effect rather than a cause the difficulty of a job causes sieve range and matrix size both. I don't think smaller sieve ranges lead to smaller matrices for a given job, though smaller Qmax to Qmin ratio seems to produce fewer duplicate relations. I testsieve to minimize total sieve time, though that's usually also when Qrange is minimized. As for recommended lim's, if I'm going above 134/134 I jump to 134/200 or 170/170 at minimum any closer to 134 and you may as well stay with 134/134 because of the speed hit you mentioned. I test 134/200 against 134/266 generally, but something like 180/220 or 200/200 might be best if 2LP on both sides the unbalanced lims work better on 3LP jobs with the small lim on the 3LP side, since the siever will pick up most of the relations that would have been lim 200M & 2LP with 134M and 3LP, at least when one prime is within [134M, 200M]. Last fiddled with by VBCurtis on 20220524 at 18:13 
20220525, 16:02  #69 
Sep 2009
3·11·73 Posts 
Thanks for the advice. I'll test sieve lims of 200M/200M against 133M/266M and see which gets the best yield. With luck I'll be able to post a job tomorrow.
I wish I knew what all the output from the siever means. It looks as if it should mean something, but most of it doesn't mean anything to me. 
20220525, 23:07  #70 
May 2009
Moscow, Russia
3·953 Posts 
QUEUED AS C184_933436_12610
C184 from 933436:i12610 is ready for GNFS: Code:
n: 4876630858212349810691213611925050755952048334305408903910300951464902067092316845896254651320465422244744087225834090890961772198806089897040721540280769008612228589646966410548502467 # skew 50681508.57, size 5.067e018, alpha 8.241, combined = 4.711e014 rroots = 5 skew: 50681508.57 c0: 110483875328199321559431815261460398065873320 c1: 64383384366687242237371786946650854654 c2: 761645235654446236920932275627 c3: 82055981426510868277147 c4: 223481580525450 c5: 8164800 Y0: 324241054145458129729151114244781903 Y1: 393459119910895718201687 rlim: 266000000 alim: 134000000 lpbr: 32 lpba: 32 mfbr: 64 mfba: 94 rlambda: 2.7 alambda: 3.6 lss: 0 type: gnfs Suggesting sieving range is 30M180M. Last fiddled with by swellman on 20220526 at 14:36 
20220526, 12:11  #71  
Jun 2012
2^{6}·59 Posts 
Quote:
I have dropped rlim to 134M. Suggest you test sieve again to generate a new yield curve. Hoping 30200M will be your new sieving range. ETA: if this job absolutely won’t fit within 15e_small then we can just move it over to 15e. Last fiddled with by swellman on 20220526 at 12:23 

20220526, 14:19  #72  
May 2009
Moscow, Russia
3×953 Posts 
Quote:


20220526, 14:51  #73 
Jun 2012
7300_{8} Posts 

20220609, 15:29  #74 
Jun 2012
111011000000_{2} Posts 
QUEUED AS 7p4_338
7+4,338 is a HCN just finishing ECM. It is a SNFS 263 job to be run on 15e_small. Code:
n: 40163610219963325261908698168315725543710527205495906950565894692963048457252960264218821247847727257524935332555526378042942452539538527605436322858575428931783709877273726423041462668170033957492670534887776342052666307717 skew: 1.0000 type: snfs size: 263 c6: 1 c5: 1 c4: 5 c3: 4 c2: 6 c1: 3 c0: 1 Y1: 42277452950578284263485622772148731904 Y0: 88124787089743477593997388358336765364597217 rlim: 134000000 alim: 134000000 lpbr: 31 lpba: 31 mfbr: 91 mfba: 62 rlambda: 3.4 alambda: 2.7 Code:
MQ Norm_yield Speed (sec/rel) 35 2093 0.220 50 1831 0.290 75 1741 0.297 100 1551 0.292 150 1343 0.404 205 1102 0.453 I will take the LA. Last fiddled with by swellman on 20220610 at 13:27 
20220614, 14:25  #75 
Jun 2012
3776_{10} Posts 
QUEUED AS 8p3_292
8+3,292 is a HCN now ready for SNFS on 15e_small. Code:
n: 267136507979524605470044357395964682249086243652588091243912977344455967651988338045265512944693533079436212360808029902035582310353325504558218309464460120217516364304443337051340619644876368298145800332116647634660653788114592729385267437199593 skew: 0.3467 type: snfs size: 264 c6: 576 c0: 1 Y1: 239299329230617529590083 Y0: 44601490397061246283071436545296723011960832 rlim: 134000000 alim: 134000000 lpbr: 31 lpba: 31 mfbr: 91 mfba: 62 rlambda: 3.4 alambda: 2.7 Code:
MQ Norm_yield Speed (sec/rel) 35 1875 0.300 50 1691 0.339 75 1531 0.361 100 1389 0.403 140 1257 0.595 180 1203 0.507 205 1060 0.629 Last fiddled with by swellman on 20220614 at 14:32 
20220617, 10:18  #76 
Jun 2012
3776_{10} Posts 
QUEUED AS 7p5_317
7+5,317 is a HCN ready for SNFS on 15e_small. Code:
n: 8005250922964400623653409089801614163844341926791193708170502887552253315908849909972739725496845462858419218045491332116038813116004297778170450465664390084878683606503403611971956761968587663149 skew: 1.0577 type: snfs size: 267 c6: 5 c0: 7 Y1: 11102230246251565404236316680908203125 Y0: 616873509628062366290756156815389726793178407 rlim: 134000000 alim: 134000000 lpbr: 32 lpba: 32 mfbr: 94 mfba: 64 rlambda: 3.5 alambda: 2.8 Code:
MQ Norm_yield Speed (sec/rel) 35 3105 0.220 50 3184 0.204 75 2724 0.228 100 2682 0.256 140 2237 0.343 180 2025 0.333 205 2007 0.334 Last fiddled with by swellman on 20220617 at 10:21 
20220621, 12:08  #77 
Jun 2012
2^{6}×59 Posts 
QUEUED AS 11p2_257
11+2,257 from the HCN project is ready for SNFS on 15e_small. Code:
n: 3558673052264700164798309434496977032392885183395428816268310259594883831061052005721913652349571099501066977072009019675667943856066053787793760072797782324893647284132923852503247722872061024557 type: snfs size: 267 skew: 1.3286 c6: 2 c0: 11 Y1: 8796093022208 Y0: 602400691612421918536387328824478011400331731 rlim: 134000000 alim: 134000000 lpbr: 32 lpba: 32 mfbr: 94 mfba: 64 rlambda: 3.5 alambda: 2.9 Code:
MQ Norm_yield Speed (sec/rel) 35 3194 0.227 50 2906 0.275 75 2756 0.296 100 2484 0.342 140 2227 0.382 180 2015 0.415 205 1935 0.443 Last fiddled with by swellman on 20220621 at 12:15 
Thread Tools  
Similar Threads  
Thread  Thread Starter  Forum  Replies  Last Post 
2022 Queue management of 15e  swellman  NFS@Home  174  20221207 14:41 
Queue management for 14e queue  VBCurtis  NFS@Home  166  20221129 10:13 
Queue management for 16e queue  VBCurtis  NFS@Home  149  20221102 11:09 
Queue management for e_small and 15e queues  VBCurtis  NFS@Home  254  20220102 01:59 
Improving the queue management.  debrouxl  NFS@Home  10  20180506 21:05 