View Single Post
Old 2020-05-06, 13:55   #102
Apr 2020

109 Posts

Originally Posted by VBCurtis View Post
I see no reason for lim's to change when LP changes. Let's leave lim's alone for now.

Your test for Q=500k vs 5M is awesome, and conclusive! 2% more uniques for the same sieve time. Let's use Q=5M for this size, pending further investigation (say, 4M or 7M or 10M may be yet better).

I agree that test-sieving on ncurves will work- but not a test-sieve at a single Q value. If I did it, I'd want 3 Q's early-mid-late job; in your case, 20-50-80M would convince me. Chances are that what's fastest at one will be fastest at another Q, but I don't think it's obvious that it has to happen that way.

I'll post a new params.c180 soon with 31/31LP this afternoon. Progress!

As for finding the 2LP/3LP crossover, we only need to test every 5 digits since that's how the params files are organized. The work we're doing could be used to generate e.g. params.c178, which CADO would recognise and use for specifically 178-digit inputs, but the maintainers have already told me not to submit any such params files. Seems like overkill, even for us.
So like this?

tasks.I = 15
tasks.qmin = 5000000 # subject to further investigation
tasks.lim0 = 90000000
tasks.lim1 = 125000000
tasks.lpb0 = 31
tasks.lpb1 = 31
tasks.sieve.mfb0 = 58 # or 59
tasks.sieve.mfb1 = 90
tasks.sieve.ncurves0 = 20
tasks.sieve.ncurves1 = 13
tasks.sieve.qrange = 10000
charybdis is offline   Reply With Quote