![]() |
[QUOTE=Plutie;586871]Would it be possible to for me to take 501__719_13m1?[/QUOTE]
Yes, quite possible. But you’ll need credentials from Greg who runs NFS@Home, unless you’ve already got them. If you’re still interested I’ll contact you via PM. |
519__511_7m1 factored
1 Attachment(s)
[QUOTE=richs;586368]Taking 519__511_7m1[/QUOTE]
[CODE]p70 factor: 5848154131191689267467694179951968309131812767388176684996493674814591 p80 factor: 53487690351394622212150053021845692715807845271076173219665934912819279028803491[/CODE] Approximately 9 hours on 6 threads of a Core i7-10510U with 12 GB memory for a 3.26M matrix at TD=100. Log attached and at [URL="https://pastebin.com/JXijWNbC"]https://pastebin.com/JXijWNbC[/URL] Factors added to factordb. |
501__719_13m1 factored
[url]https://pastebin.com/cws9Vpq3[/url]
1hr solve with Ryzen 5 5600X, -t 12 (interestingly enough, msieve said it started LA with 32 threads.) [CODE]Wed Sep 1 12:24:24 2021 p66 factor: 835251703114664138903805818363298898165852843334338964427706930837 Wed Sep 1 12:24:24 2021 p84 factor: 247795720473845772532126989395273376306177110708302852431490576685216571436579323673[/CODE] |
575709019_23m1 factored
1 Attachment(s)
[QUOTE=richs;586657]Taking 575709019_23m1[/QUOTE]
[CODE]p58 factor: 4312240442218107411934215116913778361305217663632804490281 p108 factor: 621963366116136291084199274574035422938677914793836688607419814153245743699520065579052475861945328614366719[/CODE] Approximately 22 hours on 6 threads of a Core i7-10510U with 12 GB memory for a 4.80M matrix at TD=110. Log attached and at [URL="https://pastebin.com/wxkxKvCr"]https://pastebin.com/wxkxKvCr[/URL] Factors added to factordb. |
Taking 417__011_3m1
|
Taking 184__151_5m1
|
[SIZE=2]C161_79_97 com[/SIZE][SIZE=2]pleted - nearly 5.5 hours on Tesla K80/P4 for 4.3M matrix (TD=140).[/SIZE]
[CODE]p65 factor: 28828779633629714746232507279378339304568987329836097491210549533 p97 factor: 1185168248619384757422491263883621255347347942771171906521602552051554141566065491071327103160459 [/CODE] I'm experimenting with msieve-gpu on Google Colab. LA didn't run with default settings due to "not enough memory" error, so I use "block_nnz=100000000" option. Unfortunately I'm on free account and managed to get only K80/P4 gpu's for ~3 hours/day. [URL]https://pastebin.com/dvPxwsJ2[/URL] |
C157_79_87 completed - 24 hours for 4.8M matrix (TD=100)
[CODE]p69 factor: 470334053701387388558622053730510085941350039911940492821333612624189 p89 factor: 10528298436721706770875683105253827798822788455415355624688896748407395125542180548032311 [/CODE][URL]https://pastebin.com/y4YNyqHw[/URL] |
417__011_3m1 problem
Something is not right with the relations or the .ini or .fb files for 417__011_3m1:
[CODE]Fri Sep 10 16:56:43 2021 Fri Sep 10 16:56:43 2021 Fri Sep 10 16:56:43 2021 Msieve v. 1.53 (SVN 988) Fri Sep 10 16:56:43 2021 random seeds: 7c4b4360 67ec101d Fri Sep 10 16:56:43 2021 factoring 931716212649329827085826874632296805522376190752443111047033777427443503981234835282738781393247938253896381553901865467679801153870597073922973731405293 (153 digits) Fri Sep 10 16:56:44 2021 searching for 15-digit factors Fri Sep 10 16:56:44 2021 commencing number field sieve (153-digit input) Fri Sep 10 16:56:44 2021 R0: -607288295848199450676009139407 Fri Sep 10 16:56:44 2021 R1: 204889130532497 Fri Sep 10 16:56:44 2021 A0: 17500403064728538394138027311449717866616 Fri Sep 10 16:56:44 2021 A1: 5584264633247370913975802344435818 Fri Sep 10 16:56:44 2021 A2: 292017629100948579858061139 Fri Sep 10 16:56:44 2021 A3: -25997407300505227152 Fri Sep 10 16:56:44 2021 A4: -203479838212 Fri Sep 10 16:56:44 2021 A5: 11280 Fri Sep 10 16:56:44 2021 skew 23852827.67, size 6.655e-015, alpha -8.500, combined = 3.359e-012 rroots = 5 Fri Sep 10 16:56:44 2021 Fri Sep 10 16:56:44 2021 commencing relation filtering Fri Sep 10 16:56:44 2021 setting target matrix density to 100.0 Fri Sep 10 16:56:44 2021 estimated available RAM is 12041.5 MB Fri Sep 10 16:56:44 2021 commencing duplicate removal, pass 1 Fri Sep 10 16:56:44 2021 error -11 reading relation 0 Fri Sep 10 16:56:44 2021 error -11 reading relation 1 Fri Sep 10 16:56:44 2021 error -11 reading relation 2 Fri Sep 10 16:56:44 2021 error -11 reading relation 3 ... Fri Sep 10 17:11:15 2021 error -11 reading relation 2942819 Fri Sep 10 17:11:15 2021 error -11 reading relation 2942820 Fri Sep 10 17:11:15 2021 error -11 reading relation 2942821 [/CODE] Every relation is giving an error -11. I checked the .ini and .fb files, and they are the ones on the NFS@Home server. Any ideas? |
This is odd. When the number was first created and moved into sieving, it had the following as the polynomial:
[CODE]$ cat download/267/417__011_3m1.poly n: 989163617066470014099816140104529067772498166299400837090638230533961107703370734574964910904703319468717321087072690489227697336349353632315164593791131 lss: 0 Y0: -389754269942125777022616522063 Y1: 1402575413814821 c0: 305974442857526606299730049987152237000 c1: 276756306175520282907688238818280 c2: -7458144245467064229404252 c3: -22651676006773394051 c4: 681810683016 c5: 109980 skew: 6511026.00 type: gnfs rlim: 33500000 alim: 33500000 lpbr: 29 lpba: 29 mfbr: 58 mfba: 58 rlambda: 2.5 alambda: 2.5 [/CODE] However, by the time the first results were returned, the polynomial had been changed to [CODE]$ cat 417__011_3m1.poly n: 931716212649329827085826874632296805522376190752443111047033777427443503981234835282738781393247938253896381553901865467679801153870597073922973731405293 skew: 23852827.67 lss: 0 type: gnfs Y0: -607288295848199450676009139407 Y1: 204889130532497 c0: 17500403064728538394138027311449717866616 c1: 5584264633247370913975802344435818 c2: 292017629100948579858061139 c3: -25997407300505227152 c4: -203479838212 c5: 11280 # size 6.655e-15, alpha -8.500, combined = 3.359e-12 rroots = 5 # expecting poly E from 2.92e-12 to > 3.35e-12 rlim: 33500000 alim: 33500000 lpbr: 29 lpba: 29 mfbr: 58 mfba: 84 rlambda: 2.5 alambda: 3.4 [/CODE] However, since that change was made after it had been moved into the sieving stage (likely by moving it back to the queued stage, changing it, and moving it back to sieving again), BOINC sieved using the original polynomial. |
This is very strange. Looking back in the [URL="https://www.mersenneforum.org/showthread.php?t=25927&page=5"]14d queue management thread[/URL], it seems this job was proposed and I placed it in queue with no issues. However RichD noticed problems shortly after sieving started.
I don’t remember messing with the file once it was enqueued. No reason to do so. Very odd indeed. |
All times are UTC. The time now is 18:15. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2023, Jelsoft Enterprises Ltd.