2013-06-29, 17:29   #3
lorgix

Sep 2010
Scandinavia

3×5×41 Posts

Quote:
 Originally Posted by VBCurtis I think we both would benefit from playing with settings and finding polys for a couple of smaller numbers. Perhaps some of the heavy hitters in this forum would like to supply you and I a couple of C155-180s to poly search? We can discuss settings, try to learn what stage1 bound produces the largest rate of useful nps hits per hour of gpu time, etc. I have a c147 in my own queue; I had just done -np for 5 days for a poly when this thread began. I tried to apply what we learned last week, and restarted the search. 24 hours of -np1 with stage1 set to 2e21 (default is 2.38e22) produced roughly 700MB of hits with a 460M, which will take almost a core-week to size optimize. This makes me wonder how -np manages to do all 3 steps with just one CPU thread without massively stalling the GPU. So, my first tentative guideline is to set stage 1 norm 10x tighter than default when running -np1 on its own, and even then the cpu has no chance to keep up. Or does the -nps step work with the -t threads command? If I understand previous advice, I should not bother to npr more than, say, 500 best nps hits? -Curtis
Here are a few 157-digit GNFS candidates:
Code:
(181^103-1)/((181-1)*7417*3386023*1622748672647*767015484026387551*1656939272001358583196903067208809)
(877^79-1)/((877-1)*4583*208520387347*96078130292657*103086319456710261705085017633872730943681601)
(5591^61-1)/((5591-1)*16556099215542617537*743213379283195327995487*11686924821525596917649777)
(421^101-1)/((421-1)*3637*52859291287277*15527015834461272375419*384360771211140230121323*3103491858106402597710257788494888754189303)
They are also listed at the OPN composites page. They have each had a t50.