![]() |
![]() |
#221 |
Apr 2020
193 Posts |
![]()
Just thrown in 45 more cores to help speed things along to the finish line.
|
![]() |
![]() |
![]() |
#222 |
"Curtis"
Feb 2005
Riverside, CA
2·2,339 Posts |
![]()
We reached 540M relations, and CADO crashed on the first filtering step with this error:
Code:
Error:Filtering - Duplicate Removal, removal pass: terminate called after throwing an instance of 'renumber_t::corrupted_table' Error:Filtering - Duplicate Removal, removal pass: what(): Renumber table is corrupt: cannot find data for prime 0x28e17329 ; note: isprime(p)==0 Error:Filtering - Duplicate Removal, removal pass: Note: above 2^32 ideals or relations, add FLAGS_SIZE="-DSIZEOF_P_R_VALUES=8 -DSIZEOF_INDEX=8" to local.sh In our case, it shouldn't much matter- I'm going to use msieve for postprocessing anyway. I'll let y'all know what I've got after filtering. Edit: remdups leaves me 368.0M uniques, a pleasant 68%. Q-range was 30M to 264.6M; yield fell off quite a bit at the end. If I did this size of number again, I think I'd use A=30 for Q=30-50M to boost yield at the bottom, and I'd increase lim's by 25% or so (I used 130/180M on this job). Last fiddled with by VBCurtis on 2021-01-20 at 02:44 |
![]() |
![]() |
![]() |
#223 |
"Curtis"
Feb 2005
Riverside, CA
2×2,339 Posts |
![]()
First filtering pass:
Code:
Tue Jan 19 20:02:16 2021 begin with 368134973 relations and 408812974 unique ideals Tue Jan 19 20:08:56 2021 reduce to 136356813 relations and 139341382 ideals in 25 passes Looks like Charybdis' machines clients were still waiting, as they got work immediately. Mine are running too, so if you've moved on to other tasks don't worry about your clients. 30M relations won't take long. |
![]() |
![]() |
![]() |
#224 | |
Apr 2020
193 Posts |
![]() Quote:
Would be a good idea to set rels_wanted to something like 800M so the clients keep going, and keep running msieve filtering until you get a decent matrix. PS. most of my machines rebooted overnight to install updates, apologies |
|
![]() |
![]() |
![]() |
#225 |
"Ed Hall"
Dec 2009
Adirondack Mtns
5×727 Posts |
![]()
I'll be tasking my farm back to you shortly. The "night owl" machines were running a night project.
|
![]() |
![]() |
![]() |
#226 |
"Curtis"
Feb 2005
Riverside, CA
10010010001102 Posts |
![]()
OK, I changed target rels to 670M. I'll try msieve-filtering this afternoon at ~570M raw rels and report back.
|
![]() |
![]() |
![]() |
#227 |
"Curtis"
Feb 2005
Riverside, CA
2·2,339 Posts |
![]()
578M raw relations got me 391M uniques, and a 39.98M matrix at TD=84.
There was a deficit of 27M in relations vs ideals in the first step of filtering, so I'm continuing to sieve. I think 610M or so should be enough, and we're at 600M now, so feel free to repurpose your machines any time. I'll leave the server to run till morning (USA-pacific time), and will run a final filtering job with however many relations I have when I wake up. |
![]() |
![]() |
![]() |
#228 |
"Curtis"
Feb 2005
Riverside, CA
2×2,339 Posts |
![]()
597M relations built a 34.4M matrix at TD 100 overnight.
I lost internet connection to the CADO server overnight, so we quit serving workunits at 615M relations. That'll be enough, so we're "officially" done sieving. I'll report on the actual matrix size and ETA later today. Edit: 615M raw relations yielded 414M uniques, enough for a 31M matrix at TD 116. No ETA yet, I'll edit again in a few hours once the matrix is running. EDIT2: ETA is just under 10 days, running on all 20 cores without MPI. I recently updated that machine to Ubuntu 20.04, so I may try to get the MPI fix applied and see how msieve-MPI performs on it. Last fiddled with by VBCurtis on 2021-01-21 at 20:11 |
![]() |
![]() |
![]() |
#229 | |
"Ed Hall"
Dec 2009
Adirondack Mtns
5×727 Posts |
![]() Quote:
Code:
apt update apt install openmpi-bin openmpi-common libopenmpi-dev |
|
![]() |
![]() |
![]() |
#230 |
"Curtis"
Feb 2005
Riverside, CA
2·2,339 Posts |
![]()
No plans to use another machine- simply to MPI across the two sockets, as the reduction in cross-messaging is reported to give 15-20% speedup compared to the current "msieve -t 20" for the two ten-core sockets.
I'll play with it tonight- gotta go pick up a Ferrari this afternoon! The very best kind of errand, especially when it's not my car. :) |
![]() |
![]() |
![]() |
#231 |
Jun 2012
B9416 Posts |
![]()
Yoyo@Home is finishing the batch of base-2 Cunningham numbers (1987 edition). Should be completely finished in another week or two. Each composite in this group has survived 12000 curves @B1 = 850e6. One iteration down, five more to go. Of course that’s not counting any earlier ECM work.
Next step? Following a strategy of finish-what-you-started, I can just queue all the surviving composites back into Yoyo for another round of 0.16t65 (ETA ~13 months). Or we could select a small subset of “interesting” cases for focused ECM and eventual NFS by Greg on NFS@Home. There are two quartics - start with them? Or others? With the recent extension of the base-2 tables, do we leave some of Yoyo’s resources available to work that effort? Or is ECM on Yoyo even needed with this latest batch of Cunninghams? My opinion is to split the baby - focus on a few of the 1987 base-2 Cunninghams and leave room for other work. Feeds Greg a few more candidates by this fall and avoids flooding Yoyo’s queue. But I’m certainly no Solomon... |
![]() |
![]() |
![]() |
Thread Tools | |
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Cunningham ECM efforts | pinhodecarlos | Cunningham Tables | 7 | 2017-12-21 13:29 |
Cunningham ECM Now Futile? | R.D. Silverman | GMP-ECM | 4 | 2012-04-25 02:45 |
Cunningham Project on YouTube | Batalov | Cunningham Tables | 0 | 2012-02-26 02:58 |
Extended Cunningham or so | rekcahx | Factoring | 6 | 2011-08-19 12:45 |
Introduction: ECM work done on Cunningham Project composites | garo | Cunningham Tables | 2 | 2005-01-20 10:06 |