![]() |
I think a fast SSD is also a good investment
|
15e candidate
[b]QUEUED[/b] C258 from the OPN MWRB file for the 15e queue.
[CODE]n: 781179418496003349506957439729362314644125846732665713084339945677877536695534769067966673976364848711270869987317014615916890976022261576513712051340477201711001902632021436863584734165581130067941543990700557298855022642108654130082277009034135714427496947 # 8081^67-1, difficulty: 261.80, skewness: 0.22, alpha: 0.00 # cost: 2.01944e+19, est. time: 9616.37 GHz days (not accurate yet!) skew: 0.223 c6: 8081 c0: -1 Y1: -1 Y0: 9596573069509052763759925960743779265720881 m: 9596573069509052763759925960743779265720881 type: snfs rlim: 134000000 alim: 268000000 lpbr: 31 lpba: 31 mfbr: 62 mfba: 62 rlambda: 2.7 alambda: 2.7[/CODE] Trial sieving 5K blocks. [CODE] Q Yield. 20M 7876 60M 6619 100M 6174 150M 5348 200M 5064[/CODE] |
[QUOTE=pinhodecarlos;470291]What would be the ideal system to post process them?
OS No. Cores GB[/QUOTE] They would work very nicely on a bargainhardware.com dual-octaXeon server (I am getting about 300 hours wall-clock on one of those for a 25M matrix running -t16, and the server has 64GB RAM which is more than enough). As VBCurtis observes, any job that doesn't fit in 32GB isn't going to finish in at all reasonable time. I should probably get MPI running on my small cluster, 10Gbit Ethernet is hopefully fast enough for distributed jobs to be faster than a single machine. |
[QUOTE=axn;470297]I think a fast SSD is also a good investment[/QUOTE]
A fast SSD makes lots of use cases more fun, but not really this one: the post-processing is not done at disc-read speed, it's only seven hours to filter a 32-bit-LP job over NFS-attached-by-gigabit-Ethernet. |
[b] queued [/b] C192 from the OPN t550 file.
Sieve on the algebraic side. [CODE]n: 820509983628149599725530163725918173029946762738122115708301986910039136975437410543224106014365961176642136311025280192536397165714380410331376093613059222840844852513910582756007825506511889 # 1920647391913^19-1, SNFS-220, sieve on algebraic side lss: 0 skew: 0.01436 c6: 1920647391913 c0: -1 Y1: -1 Y0: 7085050051025406838642211594025485497 rlim: 200000000 alim: 200000000 lpbr: 31 lpba: 31 mfbr: 62 mfba: 62 rlambda: 2.7 alambda: 2.7 type: snfs [/CODE]Trial sieving 5K blocks. [CODE] Q Yield 20M 6339 60M 4756 100M 5226 150M 4506 200M 3886 250M 3441[/CODE] |
I don't think I quite believe the SNFS-220 difficulty for that one; you're sieving 1920647391913^19-1, whose log is 233.39.
(yes, the actual-underlying-number is x^18+x^17+...+x+1, but that's too high a degree polynomial for SNFS; and even in that case the log is 221.1) |
[QUOTE=fivemack;470335]I don't think I quite believe the SNFS-220 difficulty for that one; you're sieving 1920647391913^19-1, whose log is 233.39.
(yes, the actual-underlying-number is x^18+x^17+...+x+1, but that's too high a degree polynomial for SNFS; and even in that case the log is 221.1)[/QUOTE] Yep, you're right. The 220 is leftover from a previous job and I forgot to update with the correct difficulty. :smile: |
[b]QUEUED[/b] C230_125_103 is ready for SNFS on siever 14e.
[code] n: 28521135208254886087875141264196218438819741739601791217526351979867886443731933341039566099501379023881662321858577195918264461259281214303491896591716506209256818596978186504281177207888391193723137146043586679928892001115217519 # 125^103+103^125, difficulty: 253.62, anorm: 2.27e+038, rnorm: 8.45e+047 # scaled difficulty: 255.21, suggest sieving rational side # size = 1.264e-012, alpha = 0.000, combined = 1.416e-013, rroots = 0 type: snfs size: 253 skew: 4.8413 c6: 1 c0: 12875 Y1: -444089209850062616169452667236328125 Y0: 1860294571709496226110032706809177658295303 rlim: 268000000 alim: 268000000 lpbr: 32 lpba: 32 mfbr: 64 mfba: 64 rlambda: 2.8 alambda: 2.8 [/code] Test sieving on the -r side with Q in blocks of 2K [code] Q=20M 5424 Q=80M 3630 Q=150M 3634 Q=250M 3431 Q=300M 3197 [/code] Suggesting a sieving range for Q of 20M-270M with a target # rels of 480M. |
[b]queued 14e[/b] C206 from the OPN t600 file.
[CODE]n: 43054571344319562525175339557182100345885547746820995312018814147133450134181278318210442952277654977047906540754269409749233399626456182473514812378195316490859005659119939110257412086994207437024997497731 # 288624373085970303047^13-1, difficulty: 245.52, skewness: 1.00, alpha: 3.10 # cost: 5.88906e+18, est. time: 2804.31 GHz days (not accurate yet!) skew: 1.000 c6: 1 c5: 1 c4: -5 c3: -4 c2: 6 c1: 3 c0: -1 Y1: -288624373085970303047 Y0: 83304028739269378634511622067993017484210 m: 36804340438773561370108118724375481945457980663275057472108694583323303624376093452096966737343487005341177954686085944498665957272914416762648721750027055154332792938580634589018627399546646801620026670533 type: snfs rlim: 134000000 alim: 134000000 lpbr: 31 lpba: 31 mfbr: 62 mfba: 62 rlambda: 2.7 alambda: 2.7[/CODE] Trial sieving 5K blocks. [CODE] Q Yield 20M 10646 60M 8521 100M 7940 140M 6897 180M 6273[/CODE] |
15e/33 job from GNFS thread
[b]QUEUED[/b] C197_149_70 has survived ECM up to almost a full t60. Originally this job was [url=http://www.mersenneforum.org/showpost.php?p=468968&postcount=295]slated for GNFS[/url], but subsequent analysis shows the SNFS poly below is faster and has better yield.
[code] n: 18990123508557902868419834986612849212629329047848408031918356871905091180915018818857084783656883790655928770567349115604303665109625610225945717466120031386943078873289069222693826896799892056101 # 149^70+70^149, difficulty: 278.01, anorm: 9.97e+039, rnorm: -1.53e+052 # scaled difficulty: 280.04, suggest sieving rational side # size = 2.773e-014, alpha = 0.000, combined = 8.262e-015, rroots = 0 type: snfs size: 278 skew: 5.2229 c6: 35 c0: 710432 Y1: -6705343098319824504035000000000000000000000000 Y0: 119738888098469732352733201 rlim: 536000000 alim: 536000000 lpbr: 33 lpba: 33 mfbr: 66 mfba: 66 rlambda: 3.0 alambda: 3.0 [/code] Test sieving on the -r side with Q in blocks of 6K [code] Q=40M 11223 Q=100M 10841 Q=250M 9156 Q=400M 8198 Q=550M 7553 Q=700M 6760 Q=800M 6543 [/code] Not sure what is the best target number of relations for this job, so I list three scenarios. [code] # rels Q range 800M 40M-560M 900M 40M-650M 1B 40M-740M [/code] I am hoping Greg would be willing to take on postprocessing for this composite but I will reserve it if he is unable to do so. |
GNFS
[b]QUEUED[/b] C162 from the OPN t550 file.
[CODE]n: 197622873793160243807385045116819555876404845504839179857130945490044807048446484276962290305846032932712738674572189413010412263215299396255923884269732389761061 # 101575129733962903176164717219488895595781584956747683545056554733469676083500321620734233^3-1 (P90^3-1) # expecting poly E from 1.05e-12 to > 1.20e-12 # skew 6066744.05, size 1.052e-15, alpha -6.821, combined = 1.180e-12 rroots = 3 lss: 0 Y0: -15371818604016342704499800918662 Y1: 242959684100947 c0: 312205997068107821744178854799316960065 c1: -306252528432352480689437271018491 c2: -12938900013765957327549451 c3: -1397956056894758645 c4: 1818955314954 c5: 230256 skew: 6066744.05 type: gnfs rlim: 67000000 alim: 67000000 lpbr: 30 lpba: 30 mfbr: 60 mfba: 60 rlambda: 2.6 alambda: 2.6[/CODE] Trial sieving 5K blocks. [CODE] Q Yield 20M 10453 50M 8874 80M 7721 110M 8198[/CODE] |
| All times are UTC. The time now is 23:14. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.