![]() |
[QUOTE=Batalov;205602]Yes, these are exactly the numbers that I've got too, averaging (conservatively) to 1.7/q-range. I expect 25% duplications and I targeted 60M unique relations (for a nice matrix). Factor in some drop-offs.
Greg will produce most relations and it is natural for him to do algebra, so it is for him to say when to stop. Something like 46M unique will be a minimum, so 10-40M range might have been barely enough (if duplication is lower than 25% which I doubt for 14e), but it is more overhead to spread with a tight estimate, then filter and say "sieve some more, guys". (Tight sieving also leads to [URL="http://mersenneforum.org/showthread.php?p=204759"]this[/URL].)[/QUOTE] Hmm. 4788.2422 used 29 bit lp and siever 14e, but had a poly which produced *much* lower rel/Q than the one you've given for this number. It had a duplication rate of about 20% at the end of sieving. I figured that since this poly has a much greater yield, that when there are enough relations for a matrix, the duplication rate will be somewhat less than 20% (but higher with over-sieving). Would having 60M uniqs make a matrix which is enough smaller to recover from the extra sieving time? The matrix for 4788.2422 was: [QUOTE=bsquared;181375][CODE]matrix is 5525542 x 5525789 (1619.6 MB) with weight 419589043 (75.93/col) sparse part has weight 369304539 (66.83/col) [/CODE][/QUOTE] |
[QUOTE=Andi47;205580]108@43e6, no factor.[/QUOTE]Chalk up another 350 @ 43M with no factor.
|
[QUOTE=schickel;205608]Chalk up another 350 @ 43M with no factor.[/QUOTE]And another 100 from a system reporting in late.....
|
Greg, could you possibly do the whole thing? It would save making a thread, going through the uploading procedure etc.
|
[QUOTE=10metreh;205611]Greg, could you possibly do the whole thing? It would save making a thread, going through the uploading procedure etc.[/QUOTE]
That actually might be best at this point. I can finish the sieving by tomorrow afternoon anyway. Is anyone else sieving a range right now? |
[QUOTE=frmky;205645]I can finish the sieving by tomorrow afternoon anyway. [/QUOTE]
Linear algebra has started. ETA is late Wednesday. |
Sieving q=35-60M and half of q=10-25M yielded 55438411 relations. After adding 122359 free relations, 47532016 unique relations resulted. This produced a matrix, minus the first 48 rows, of 4230898 x 4231123 (1234.6 MB) with weight 319433968 (75.50/col). The matrix took 39.7 hours to solve using a 2.4 GHz Core 2 Quad. The first dependency yielded the factors:
prp75 factor: 117560800474237185708625257547574758024996437963669838128426872711607597881 prp79 factor: 3278852140305248654079854796296493405290720207444801807245306680433973717782241 Definitely out of reach of ECM. |
Nice one!
Next, c158? 1e6 and p+-1 @ 3e8 are done. |
[QUOTE=Batalov;205971]
Next, c158? 1e6 and p+-1 @ 3e8 are done.[/QUOTE] Using B1=110000000, B2=776278396540, polynomial Dickson(30), sigma=683354193 Step 1 took 633428ms Step 2 took 181107ms ********** Factor found in step 2: 17335794135816327772963766917142503900385631736928141 Found probable prime factor of 53 digits: 17335794135816327772963766917142503900385631736928141 Composite cofactor 1189490960686935297257272800772356983024280201154200068853987897043760977639076215370405965982202953034487 has 106 digits GNFS is running on the C106. prp50 factor: 20274140516912084803282588212968042860978240596053 prp56 factor: 58670352003069986061451666975983758254072741101616497179 |
I did 340 curves @ B1=11000000, B2=35133391030 on the line 2526 c128.
starting GPU poly search using -np 1,30000 |
[QUOTE=jrk;206008]I did 340 curves @ B1=11000000, B2=35133391030 on the line 2526 c128.
starting GPU poly search using -np 1,30000[/QUOTE] Sieving is already well underway. I'll have the factors by the end of the day. |
| All times are UTC. The time now is 23:10. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.