Having a hard time finding a polynomial for a C138

YuL · 2013-11-28, 21:04

I'm currently searching a polynomial for a C138 using msieve 1.52 (SVN 942)
GPU, the best thing I could get is e = 2.831e-011 whereas the expected
e is from 2.93e-011 to > 3.37e-011. Out of curiosity I ran msieve 1.51
and it says expecting poly E from 2.55e-011 to > 2.93e-011.
Any advice(s) would be appreciated.
Note: I had two instances of msieve 1.52 running on two GPUs, the default
stage 2 norm is 1.73e+019, on the various runs I've made I set
"stage2_norm=X" with X=3e+018, 7e18, 9e18.

VBCurtis · 2013-11-29, 16:01

The "expected" scores are an estimate, which at certain sizes is difficult to achieve- you have found such a size. You found a poly with a score in the range listed from v1.51- why did you say you are having a hard time, when you do actually have a poly?

If the number takes 3 days to sieve, does it matter if you've hit the target score? Would you feel better about your GPUs if you spent 36 hr finding a poly in the v1.52 window that sieves the job 4 hrs faster than the poly you have now?

YuL · 2013-11-29, 21:56

Quote:

Originally Posted by VBCurtis

The "expected" scores are an estimate, which at certain sizes is difficult to achieve- you have found such a size.

Didn't know about that, kinda explains it all...

Quote:

Originally Posted by VBCurtis

If the number takes 3 days to sieve...

It's actually worse than that, I can do sieving + LA in less than 18 hours

Quote:

Originally Posted by VBCurtis

...Would you feel better about your GPUs if you spent 36 hr finding a poly in the v1.52 window that sieves the job 4 hrs faster than the poly you have now?

Of course not, but I thought it would be possible to find a poly in the v1.52 window as I've made it for bigger numbers but then again I didn't know that the expected range is sometimes unreachable.

Thank you for your help.

jasonp · 2013-11-30, 03:16

There is another 'dead zone' around 150 digits.

You do have to be careful that polynomial selection not take much longer than it is worth, especially for jobs where the sieving would not take long even for a bad polynomial. The library tries to limit the total time spent searching for polynomials but that's not as simple as it sounds.

The measurement of E value was changed in v1.52 to match the scores produced by the CADO tools, but the process of selecting polynomials has not changed otherwise.

2013-11-28, 21:04	#1
YuL Feb 2012 Paris, France 2×3⁴ Posts	Having a hard time finding a polynomial for a C138 I'm currently searching a polynomial for a C138 using msieve 1.52 (SVN 942) GPU, the best thing I could get is e = 2.831e-011 whereas the expected e is from 2.93e-011 to > 3.37e-011. Out of curiosity I ran msieve 1.51 and it says expecting poly E from 2.55e-011 to > 2.93e-011. Any advice(s) would be appreciated. Note: I had two instances of msieve 1.52 running on two GPUs, the default stage 2 norm is 1.73e+019, on the various runs I've made I set "stage2_norm=X" with X=3e+018, 7e18, 9e18.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Can discrete logarithms / factoring be done in P (i.e., deterministic polynomial time)?	Raman	Factoring	1	2016-05-23 13:44
C138 poly selection	firejuggler	Aliquot Sequences	1	2011-02-21 06:38
Team sieve #4: c138 from 4788:2383	10metreh	Aliquot Sequences	113	2009-05-14 05:33
Hard proplem for finding sine function	tinhnho	Miscellaneous Math	6	2005-01-17 05:42
AKS - A polynomial-time algorithm for testing primality.	Maybeso	Math	11	2002-11-20 23:39

2013-11-29, 16:01	#2
VBCurtis "Curtis" Feb 2005 Riverside, CA 2²·1,409 Posts	The "expected" scores are an estimate, which at certain sizes is difficult to achieve- you have found such a size. You found a poly with a score in the range listed from v1.51- why did you say you are having a hard time, when you do actually have a poly? If the number takes 3 days to sieve, does it matter if you've hit the target score? Would you feel better about your GPUs if you spent 36 hr finding a poly in the v1.52 window that sieves the job 4 hrs faster than the poly you have now?

2013-11-30, 03:16	#4
jasonp Tribal Bullet Oct 2004 3²×5×79 Posts	There is another 'dead zone' around 150 digits. You do have to be careful that polynomial selection not take much longer than it is worth, especially for jobs where the sieving would not take long even for a bad polynomial. The library tries to limit the total time spent searching for polynomials but that's not as simple as it sounds. The measurement of E value was changed in v1.52 to match the scores produced by the CADO tools, but the process of selecting polynomials has not changed otherwise.