Improved params files for CADO

[VBCurtis]

The CADO thread contains some improved params files, such as the ones Gimarel supplied, but they're quite difficult to locate. Let's use this thread for discussions about params and improvements to the default params files.

The forum does not allow attachments with arbitrary suffixes, so remember to append .txt to the end of any params files you post!

[VBCurtis]

Attached are my best effort at parameters for C90, C95, and C100. These files all use Gimarel's excellent development with tight lambda settings near 1.80 combined with loose large-prime bounds and very low Q values.
Timing data: For C90, I ran single-threaded. The stock CADO git-install from Feb '19 took 2236 seconds, while my params took 941 seconds.
For C95 on 6 threads of an otherwise busy 6-core i7-haswell, CADO-default takes 1008 seconds while this params file takes 625 seconds.
For C100 on 6 threads, CADO-default takes 1904 seconds while this params file takes 1288 seconds. Poly-select time should probably be reduced a bit on this file, as I just noticed poly select takes 10% of sieving time.
Running multi-threaded, I believe the YAFU-CADO crossover is somewhere near 90 digits! Please run your own tests and report back here.
Edit 15 Apr: C90 file fixed to comment out the input value N. The c90 file is the one that CADO chose to explain all the parameters, so they included a sample N; I do the same.

[VBCurtis]

Attached are improved params files for C105, C110, and C115. I leave to the user to compare timings against stock files (please post results here!).
Under the conditions of these files, with low Q values and tight lambda settings, I find the crossover from I=12 to I=13 to be around 118 digits.
Edit 9 April: params.c115 was edited to change "tasks.sieve.qmin" to "tasks.qmin". CADO changed the name of this setting in 2019, and this file hadn't been updated.
Edit 13 April: params.c120 added. Tested on RSA120: Stock CADO (April '19 git) 15538 wall-clock seconds, this file 11302 seconds; measured 6-threaded on a 6-core i7 running 5xLLR concurrently.
23Apr21: Added c125 file.

[VBCurtis]

C130 params have been posted.
15 Apr edit: Tested on 6 threads i7-5820, RSA130: Apr '19 git 63043 seconds, this file 40360 seconds wall-clock time. Also, tasks.sieve.qmin changed to tasks.qmin.
22 Sep edit: C140 params added. Tested on 12 threads i7-5820, RSA140: Sep '19 git 83417 seconds, this file 62729 seconds wall-clock time.
23Apr21 edit: C135 added. Best timing 27500 sec for a C137 on 12x2.5 Haswell-Xeon.

[VBCurtis]

{post reserved for future file attachments for C145 to C165}

[VBCurtis]

Poly select params posted for C190 and C195. Sieve params are CADO default, and are not optimal.
These params take about 1/3rd the CADO-default time; if you are not impressed with the E-score from your run, double P and run again.
Thanks to user hnoey for extensive testing on a series of C193s to develop these parameters.

[VBCurtis]

The current git release for CADO has a note in the params.c120 file that says they've verified experimentally that matrix density 100 is optimal at that size. I haven't tested it yet, but my files use densities of 135-155; if 100 proves faster, I'll be updating all of the files.

CADO originally used 170 for all sizes; I thought I was already using a pretty low density...

[EdH]

This is from the unmodified params files in the Development version runs I posted in the CADO-NFS thread. I should have some comparison modified params runs soon:

dig   cpu/elapsed time
---   ----------------------
74    1245.62/49.9081
75    1579.75/41.1682
75    1484.11/45.9239
79    2170.13/54.9493
79    1780.97/60.1481
80    2431.27/58.9629
80    2206.38/67.7262
80    1904.68/66.3247
80    2046.36/64.2789
80    2471.99/67.8799
80    2159.99/72.5948
82    2354.01/58.6331
84    2559.15/62.1541
84    3038.62/78.0739
85    3400.2/78.9644
85    3504.66/85.8065
86    3518.26/98.8682
86    3655.63/89.1821
86    4071.04/106.596
86    4017.55/100.512
86    3184.24/74.8409
87    4202.14/128.446
87    3997.62/236.189
88    5078.94/138.644
90    6581.7/129.619
90    6786.46/160.069
91    6789.82/140.023
91    6685.29/134.413
94    10033.3/251.869
94    7691.76/212.026
94    9167.48/236.614
94    10231/247.654
94    9694.67/259.649
95    11464.4/230.579
96    12163.4/232.13
96    11602.3/273.837
96    12517.3/233.369
96    10671.7/253.824
97    13343.6/248.417
98    15737/328.048
98    14776.7/296.881
98    14768.1/347.099
99    16861.4/375.305
99    14919.2/375.983
100    18859.4/378.495
102    23535.8/491.217
102    22007.8/400.009
102    23544.4/531.072
102    21766.3/459.406
102    22909.6/438.363
103    19677.6/544.91
103    19994.5/614.039
104    22606.8/618.271
105    25752.2/657.456
107    32252.9/641.667
108    33323.8/719.982
108    29268/614.038
110    36442/874.006
110    39789.6/904.136
111    39385.7/985.466
113    59437.2/1206.31
114    62543.9/1259.54
114    63621.9/1721.12
115    63498.4/1682.17
117    87274.5/1820.56
117    78749.6/1779.51
117    88810.1/2200.56
118    96917.9/1977.22
118    101399/2625.73
119    116296/2590.59
120    107719/2345.83
120    110556/2303.2
120    129214/2763.6
121    139975/2996.79
121    141585/3000.22
122    146063/2690.93
123    181634/4156.62
124    205371/4196.39
125    183532/4387.97
126    209732/4763.29
127    281775/5911.33
127    279243/6556.18
128    301283/11037
128    283924/10980.6
129    304850/10683
129    307423/10925.6
130    374315/9931.01
131    418847/14039.8
133    551879/12586.8
135    680225/16017.4
138    709733/16633.3

If you need/want to move this elsewhere, go ahead.

[EdH]

Originally Posted by VBCurtis

...
Edit 9 April: params.c115 was edited to change "tasks.sieve.qmin" to "tasks.qmin". CADO changed the name of this setting in 2019, and this file hadn't been updated.
...

It looks like c130 also needs this edit.

[EdH]

Hi Curtis,

Your params.c90.txt file appears to have an N value within...

-Ed

[VBCurtis]

Originally Posted by EdH

Hi Curtis,

Your params.c90.txt file appears to have an N value within...

-Ed

Fixed! I simply commented out the N value, as CADO itself does for the c90 default file.
Also, the line to add to a work file to *not* use /tmp for all work is tasks.workdir = ./{jobfoldername}
If you don't use work files, you can pass any param flag to CADO on the command line by prepending with double-dash: ./cado-nfs.py {input number} --tasks.workdir=./{jobfoldername}
Default CADO behavior is to use /tmp directories for all job data; a power loss during a job eradicates all progress. The downside to using your own directories within /cado-nfs is that you must remember to delete the data after jobs finish, else you'll run out of disk space.