![]() |
![]() |
#12 |
Aug 2020
79*6581e-4;3*2539e-3
24×41 Posts |
![]()
No new primes for n < 3,600,000
Largest n in progress = 3,875,000 # of digits = 1,166,500 (rank: ~ 325) FFT size = 400k Avg. time = 4970 s Smallest n in progress = 3,600,000 # of digits = 1,085,000 (rank: ~ 395) FFT size = ---k Avg. time = ---- s Around July all sieved candidates of n < 4,100,000 should have been tested. I'm not so optimistic anymore that a prime will turn up... Last fiddled with by bur on 2021-05-03 at 07:49 |
![]() |
![]() |
![]() |
#13 |
Aug 2020
79*6581e-4;3*2539e-3
12208 Posts |
![]()
Things progressed much faster than I expected, the last batch 4,095e6 < n < 4,100e6 will be assigned to a core today and everything should be finished until June, 10th.
If there will be no prime in these last few numbers, I'll continue by sieving the proth side to higher n and doing LLR on-the-fly depending on sieve/LLR times as LaurV suggested. According to prime95 I'll be able to continue single-threaded until an FFT size of 640k is reached which will be around n = 5.6e6, which agrees nicely with the 5.3 MB of L3 each core has. I just hope a prime will turn up before testing becomes really slow. I'm set on finding a mega prime for this k though. :D Last fiddled with by bur on 2021-05-29 at 07:08 |
![]() |
![]() |
![]() |
#14 |
Aug 2020
79*6581e-4;3*2539e-3
12208 Posts |
![]()
All n < 4,100,000 have been tested, no new primes other than the ones already posted.
Currently I'm sieving in the range of 4,100,000 < n < 10,000,000. Smallest p-P range in progress: 87E12-107E12 Avg. time per factor: 810 s Largest p-P range in progress: 310E12-330E12 Avg. time per factor: 3160 s Remaining candidates: 100,936 / 5,900,000 (1.71%) Est. time per LLR test of smallest candidate: 5600 s (n = 4,100,014) |
![]() |
![]() |
![]() |
#15 |
Aug 2020
79*6581e-4;3*2539e-3
24·41 Posts |
![]()
Quick update, no new primes...
All n < 4,300,000 have been tested. n < 10,000,000 sieved up to 570E12 (10,000 s / factor) Approximately 90,000 candidates remain. Largest LLR-test currently running: n = 4,450,000 FFT = 448k 6200 s / test Caldwell entry rank: 290 If the LLR-runtime would increase strictly quadratic, then it'll take to around n = 5,600,000 until an LLR test takes again as long as sieving to eliminate a candidate. As a very rough estimate that should take about 7 months on the 10 core. And when will the next prime appear? Judging from Primegrid's results on other prime k values it can be a looong time. |
![]() |
![]() |
![]() |
#16 |
Aug 2020
79*6581e-4;3*2539e-3
65610 Posts |
![]()
To keep up with the roughly monthly updates and since it's been one year now since I started searching this k, here are the current stats:
As always, no new prime. All n < 4,600,000 have been tested. Largest LLR-test currently running: n = 4,790,000 FFT = 512k 7500 s / test Caldwell entry rank: 274 Last fiddled with by bur on 2021-08-27 at 17:15 |
![]() |
![]() |
![]() |
#17 |
Aug 2020
79*6581e-4;3*2539e-3
29016 Posts |
![]()
Once again, a status update with no new prime:
Sieving All n < 10,000,000 have been sieved to 800e12. Last reported time per factor: approx. 12,000 s 76,167 candidates (1.6%) are left in the range 5,250,000 < n < 10,000,000. LLR All n < 5,250,000 have been tested. Smallest LLR-test currently running: n = 5.25M FFT = 560k duration = 9975 s / test digits = 1.58M Caldwell entry rank: 254 Largest LLR-test currently running: n = 5.36e6 FFT = 560k duration = 10100 s / test digits = 1.61M Caldwell entry rank: 252 |
![]() |
![]() |
![]() |
#18 |
"Mark"
Apr 2003
Between here and the
154628 Posts |
![]()
If you have a GPU, use srsieve2cl for sieving. Depending upon the GPU, it might be faster than sr1sieve. I have a mid-range GPU and it is 5x faster than sr1sieve on the same CPU.
|
![]() |
![]() |
![]() |
#19 |
"AMD YES!"
Jan 2020
Bellevue, WA
83 Posts |
![]()
Where can srsieve2cl be obtained?
Last fiddled with by dannyridel on 2021-11-24 at 00:51 |
![]() |
![]() |
![]() |
#20 |
"Mark"
Apr 2003
Between here and the
696210 Posts |
![]()
It is part of mtsieve and can be found here: https://sourceforge.net/projects/mtsieve/
|
![]() |
![]() |
![]() |
#21 | |
"AMD YES!"
Jan 2020
Bellevue, WA
5316 Posts |
![]() Quote:
|
|
![]() |
![]() |
![]() |
#22 |
"Alexander"
Nov 2008
The Alamo City
2·33·17 Posts |
![]()
Not to hijack this thread, but based on personal experience, I've had trouble getting my GeForce RTX 2060 to sieve faster with srsieve2cl than my Intel Core i7-10875H running 8 threads with sr1sieve. In fact, it's not even close with my Riesel data (at least 2-to-1 IIRC).
|
![]() |
![]() |
![]() |
Thread Tools | |
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Proth primes | ET_ | Proth Prime Search | 15 | 2022-06-26 03:27 |
Proth 2.0 | pepi37 | Software | 10 | 2020-09-06 17:26 |
Proth and Riesel Primes | lukerichards | Number Theory Discussion Group | 7 | 2018-01-20 16:47 |
(NEW) Proth Primes Section | kar_bon | Riesel Prime Data Collecting (k*2^n-1) | 6 | 2010-11-25 13:39 |
some primes I found with Proth.exe last year | ixfd64 | Lounge | 1 | 2005-09-07 23:42 |