Primo

[Jayder]

Is anybody currently working on the PRPs <= 3000? I may do a little or a lot of work, and I don't want to run into anyone.

[chris2be8]

I'm working on them from the bottom up. If you keep away from the lowest few hundred PRPs you should be OK (anything over 1500 digits should be safe for at least a month).

[kruoli]

Currently, I am running a certification on Sm(2445)*10^8677+Smr(2446). While the system I am running it on has a throughput of slightly above one 10k digit number per day, it now stands at 46806/57633 bits in phase 1 after more than a week (slightly above eight days). This is with the same number of threads as with the 10k candidates. Even if I assume that Primo operates in \(\mathcal{O}(\log(n)^{5+\varepsilon})\) for small \(\varepsilon\) instead of \(\mathcal{O}(\log(n)^{4+\varepsilon})\), this seems way slower than it should be expected. Is my expectation flawed (maybe I computed the ETA wrong) or is there something else that could slow it done?

I know that ECPP is non-deterministic algorithm and I might got an extreme sample here. Can somebody chime in if this might be the case?

[paulunderwood]

Originally Posted by kruoli

Currently, I am running a certification on Sm(2445)*10^8677+Smr(2446). While the system I am running it on has a throughput of slightly above one 10k digit number per day, it now stands at 46806/57633 bits in phase 1 after more than a week (slightly above eight days). This is with the same number of threads as with the 10k candidates. Even if I assume that Primo operates in \(\mathcal{O}(\log(n)^{5+\varepsilon})\) for small \(\varepsilon\) instead of \(\mathcal{O}(\log(n)^{4+\varepsilon})\), this seems way slower than it should be expected. Is my expectation flawed (maybe I computed the ETA wrong) or is there something else that could slow it done?

I know that ECPP is non-deterministic algorithm and I might got an extreme sample here. Can somebody chime in if this might be the case?

I found log^4 is a good rule of thumb. Have you selected max settings on the certification page? 11k dd? (?). Things will speed up! I know it can be disheartening to watch it backtrack, A watched kettle never boils!

[kruoli]

Yes, I used 11k digits and the maximum setting in the other field.

Watching it is only fun when it has sped up considerably towards the end of phase 1.

[Batalov]

Originally Posted by kruoli

Watching it is only fun when...

... you pressed the button "Start".
You job was already done then.

Unless you also watch the paint dry. (assuming you ever painted walls)

[chris2be8]

@Ray Chandler, would you mind moving to slightly larger numbers? My script has reached 1519 digits and I've seen it try to process some numbers you had just submitted certificates for. It would avoid the bad case of us both generating certificates for the same number at the same time.

[sweety439]

Currently the primes (2^42737+1)/3 and (2*10^19153+691)/9 have no certificates in factordb, and their status are still "PRP" in factordb, however, both of them are in fact proven primes, see http://www.lix.polytechnique.fr/Labo.../myprimes.html, but when I download their certificates (the original link of certificates of (2^42737+1)/3 was broken, clink this new link to download, and for the other number (2*10^19153+691)/9, click this link to download) and upload them to factordb, factordb says "not PRIMO certificates" and neither certificates can be uploaded to factordb.

[EdH]

Originally Posted by sweety439

Currently the primes (2^42737+1)/3 and (2*10^19153+691)/9 have no certificates in factordb, and their status are still "PRP" in factordb, however, both of them are in fact proven primes, see http://www.lix.polytechnique.fr/Labo.../myprimes.html, but when I download their certificates (the original link of certificates of (2^42737+1)/3 was broken, clink this new link to download, and for the other number (2*10^19153+691)/9, click this link to download) and upload them to factordb, factordb says "not PRIMO certificates" and neither certificates can be uploaded to factordb.

Did you unpack them first? Did they look like:

[PRIMO - Primality Certificate]
Version=4.3.0 - LX64
WebSite=http://www.ellipsa.eu/
Format=4
ID=B3F5C051930D8
Created=Feb-26-2019 11:45:39 PM
TestCount=321
Status=Candidate certified prime

[Comments]
Put here any comment...

[Running Times (Wall-Clock)]
1stPhase=6709s
2ndPhase=1902s
Total=8611s

[Running Times (Processes)]
1stPhase=24918s
2ndPhase=7447s
Total=32365s

[Candidate]
. . .

[sweety439]

Originally Posted by EdH

Did you unpack them first? Did they look like:

[PRIMO - Primality Certificate]
Version=4.3.0 - LX64
WebSite=http://www.ellipsa.eu/
Format=4
ID=B3F5C051930D8
Created=Feb-26-2019 11:45:39 PM
TestCount=321
Status=Candidate certified prime

[Comments]
Put here any comment...

[Running Times (Wall-Clock)]
1stPhase=6709s
2ndPhase=1902s
Total=8611s

[Running Times (Processes)]
1stPhase=24918s
2ndPhase=7447s
Total=32365s

[Candidate]
. . .

I unpack the .gz files, and find a folder containing a .certif file, I change the ".certif" to ".zip" and uploaded them to factordb

[paulunderwood]

Originally Posted by sweety439

I unpack the .gz files, and find a folder containing a .certif file, I change the ".certif" to ".zip" and uploaded them to factordb

gunzip the .gz files. Then zip the .certif up to .zip. No need to rename anything