mersenneforum.org

mersenneforum.org (https://www.mersenneforum.org/index.php)
-   Conjectures 'R Us (https://www.mersenneforum.org/forumdisplay.php?f=81)
-   -   Riesel base 3 reservations/statuses/primes (https://www.mersenneforum.org/showthread.php?t=11151)

gd_barnes 2021-01-10 08:38

That must be a fast siever.


I will have to try a range with srsieve on my new Ryzen 9 that I just got 3 months ago.

rogue 2021-01-13 18:09

[QUOTE=rogue;568734]I will revise my estimate to about 32G per day as opposed to what I wrote yesterday. It is easier to get accurate numbers after many hours of runtime. Here is the current line:

p=61209583927, 14.10K p/sec, 83052 factors found at 1.43 sec per factor (last 134 min)

so it has been running a little under 20 hours.[/QUOTE]

Still running. I had to stop to install Windows updates, but there are about 3.37m candidates remaining so it has removed about 300,000 candidates in about 5 days.

p=308438889503, 28.20K p/sec, 64097 factors found at 3.90 sec per factor (last 1005 min)

rogue 2021-01-20 15:50

[QUOTE=rogue;569188]Still running. I had to stop to install Windows updates, but there are about 3.37m candidates remaining so it has removed about 300,000 candidates in about 5 days.

p=308438889503, 28.20K p/sec, 64097 factors found at 3.90 sec per factor (last 1005 min)[/QUOTE]

Still running:

p=702338392703, 25.26K p/sec, 8318 factors found at 9.99 sec per factor (last 1125 min)

It is down to about 3.2m candidates. I will stop when the removal rate reaches about 1 factor per 15 seconds.

gd_barnes 2021-01-22 01:58

[QUOTE=rogue;569720]Still running:

p=702338392703, 25.26K p/sec, 8318 factors found at 9.99 sec per factor (last 1125 min)

It is down to about 3.2m candidates. I will stop when the removal rate reaches about 1 factor per 15 seconds.[/QUOTE]

Why 15 seconds? Tests for R3 at n=75K-80K run about 6-8 secs on a modern I7-9700 with all cores running. Plus there are many tests that will be removed by k's found prime. You could have probably justified stopping at a removal rate of 5 secs

I suppose that maybe you will be testing on slower machines, which maybe makes 15 secs better. But just thought I'd point it out.

rogue 2021-01-22 04:02

[QUOTE=gd_barnes;569804]Why 15 seconds? Tests for R3 at n=75K-80K run about 6-8 secs on a modern I7-9700 with all cores running. Plus there are many tests that will be removed by k's found prime. You could have probably justified stopping at a removal rate of 5 secs

I suppose that maybe you will be testing on slower machines, which maybe makes 15 secs better. But just thought I'd point it out.[/QUOTE]

Now you tell me! :-)

15 seconds is the time for a single test on this laptop at n=80000.

I'll switch over to testing the range.

gd_barnes 2021-01-22 05:22

My rule of thumb for CRUS: Sieve on my fastest sieving machine until the removal rate equals the test time of a candidate at 50-60% of the n-range of the average of the machines that I will be testing on. Those machines that I will be testing on may or may not include the fastest siever.

I just checked out all that sieving that I did for R3 using my newer Ryzen 9...a machine that I did not have when I did the sieving. Since it's an AMD it should be somewhat faster at sieving than Intels by my experience. It was. Using srsieve at P=35G I was getting a test removed every ~9 seconds. Using the Intel that I had used before it was about every ~10-12 seconds.

With an average test time of 6-8 seconds at n=70K-80K as stated previously, from my perspective P=35G was slightly over-sieved for the entire k=25G-55G range.

I wanted to check it with the Ryzen in case it was significantly faster and I could justify sieving some more. It wasn't enough faster to do so.

From your perspective it looks like you could have stopped sieving at P=~400G somewhere using your super speedy siever assuming that your average test time is similar to mine. Anyway...just food for thought if you sieve k=36G-37G for your next set of testing.

rogue 2021-01-22 13:21

I only have one machine that can sieve 4000 or so sequences (enough for a 1G range of R3) in the GPU. I just kicked off the 36G range.

Since I will be using PRPNet to manage the testing, I can statistics in the database to estimate the average PRP test on the same computer. After a few days (or a week) I should have enough data to determine the optimal factor removal rate, although I believe that your estimate of 400G is very close.

rogue 2021-01-26 14:54

On the computer where I'm doing the sieving tests take about 12.5 each on average.

But since I have multiple computers, the average across all of the cores is 7.5 seconds per test. That is my sieving target removal rate.

In short, if using srsieve2cl, this is going to be based upon the average test time of the various cores you are using for PRP testing.

With my cores a range of 1G will take about 17 days of PRP testing.

rogue 2021-02-02 15:56

[QUOTE=rogue;570147]On the computer where I'm doing the sieving tests take about 12.5 each on average.

But since I have multiple computers, the average across all of the cores is 7.5 seconds per test. That is my sieving target removal rate.

In short, if using srsieve2cl, this is going to be based upon the average test time of the various cores you are using for PRP testing.

With my cores a range of 1G will take about 17 days of PRP testing.[/QUOTE]

For my setup the optimal sieve depth is between 500e9 and 550e9.

rogue 2021-02-05 15:17

1 Attachment(s)
R3 35G is done to n=100000. Primes are attached.

Gary, do you want residues for this range?

gd_barnes 2021-02-05 22:00

[QUOTE=rogue;570917]R3 35G is done to n=100000. Primes are attached.

Gary, do you want residues for this range?[/QUOTE]
Yes

Are you reserving the next 1G range? Or should I just wait until you reserve each range?

rogue 2021-02-05 22:55

[QUOTE=gd_barnes;570948]Yes

Are you reserving the next 1G range? Or should I just wait until you reserve each range?[/QUOTE]

I will send the residues via e-mail.

I reserved the entire range from 35G to 45G. Based upon the first 1G range I estimate about 14 days per 1G.

gd_barnes 2021-02-06 00:33

[QUOTE=rogue;570951]I will send the residues via e-mail.

I reserved the entire range from 35G to 45G. Based upon the first 1G range I estimate about 14 days per 1G.[/QUOTE]
Oh OK. I'll note that.

rogue 2021-02-14 14:17

1 Attachment(s)
R3 36G primes attached.

rogue 2021-02-23 16:13

1 Attachment(s)
R3 37G primes attached.

rogue 2021-03-03 19:13

1 Attachment(s)
R3 38G primes attached

rogue 2021-03-12 16:16

1 Attachment(s)
R3 39G primes attached.

In case anyone is wondering, I have been sending residues to Gary via e-mail.

rogue 2021-03-19 17:06

1 Attachment(s)
R3 40G primes attached

rogue 2021-04-01 12:31

1 Attachment(s)
R3 41G primes attached.

rogue 2021-04-02 18:51

1 Attachment(s)
R3 42G primes attached.

rogue 2021-04-08 11:28

1 Attachment(s)
R3 43G primes attached.

rogue 2021-04-15 02:57

1 Attachment(s)
R3 44G primes attached. My reservation is released.

gd_barnes 2021-04-15 09:52

[QUOTE=rogue;575930]R3 44G primes attached. My reservation is released.[/QUOTE]

Wrong file. This is the one for k=43G-44G. :-)

rogue 2021-04-15 11:56

1 Attachment(s)
[QUOTE=gd_barnes;575945]Wrong file. This is the one for k=43G-44G. :-)[/QUOTE]

Sorry. Here you go.

gd_barnes 2021-04-15 20:12

[QUOTE=rogue;575948]Sorry. Here you go.[/QUOTE]


Nice work on the reservation Mark! :smile:

rogue 2021-04-15 22:39

[QUOTE=gd_barnes;575980]Nice work on the reservation Mark! :smile:[/QUOTE]

Hopefully others decide to take up the mantle for R3 so that we can knock out that project goal for 2021. I fear that the BOINC project for 25G-35G won't finish in 2021 given its current rate.

Maybe next year S3 to n=50000 will be on the list. That is probably about the same amount of work as taking R3 from 50000 to 100000.

pokemonlover123 2021-04-16 20:26

[QUOTE=rogue;575986]Hopefully others decide to take up the mantle for R3 so that we can knock out that project goal for 2021. I fear that the BOINC project for 25G-35G won't finish in 2021 given its current rate.

Maybe next year S3 to n=50000 will be on the list. That is probably about the same amount of work as taking R3 from 50000 to 100000.[/QUOTE]


How would I be able to help? I haven't done this before but if I can I'd like to try to assist.

pokemonlover123 2021-04-17 21:26

Looks like I've got everything in order and crunching! Since that's the case, I'd like to reserve the 45G range (I know that means 45G to just below 46G). I understand I would post the primes found in a file here right? What about residues? Is there anything else I have to send once the range is done?

rogue 2021-04-17 23:41

[QUOTE=pokemonlover123;576072]Looks like I've got everything in order and crunching! Since that's the case, I'd like to reserve the 45G range (I know that means 45G to just below 46G). I understand I would post the primes found in a file here right? What about residues? Is there anything else I have to send once the range is done?[/QUOTE]

Gary wants the residues for k without a prime. If using PRPNet this SQL will pull them out of the database:

[CODE]select c.CandidateName, ctr.Residue from CandidateTestResult ctr, Candidate c, CandidateGroupStats cgs where c.CandidateName = ctr.Candidatename and c.k = cgs.k and c.b = cgs.b and c.c = cgs.c and (cgs.SierpinskiRieselPrimeN = 0 or c.n < cgs.SierpinskiRieselPrimeN)[/CODE]

gd_barnes 2021-04-18 00:21

[QUOTE=pokemonlover123;576072]Looks like I've got everything in order and crunching! Since that's the case, I'd like to reserve the 45G range (I know that means 45G to just below 46G). I understand I would post the primes found in a file here right? What about residues? Is there anything else I have to send once the range is done?[/QUOTE]

Welcome to CRUS pokemonlover! :smile:

I'll go ahead and reserve k=45G-46G for you. We assume that you have at least 4 cores to run on the effort. As rogue (Mark) said that would likely take a couple of months running everything 24x7.

You can post all residues if that is easier or just post residues for k's without primes. Either is fine.

Have fun!

Gary

pokemonlover123 2021-04-18 00:37

[QUOTE=gd_barnes;576082]Welcome to CRUS pokemonlover! :smile:

I'll go ahead and reserve k=45G-46G for you. We assume that you have at least 4 cores to run on the effort. As rogue (Mark) said that would likely take a couple of months running everything 24x7.

You can post all residues if that is easier or just post residues for k's without primes. Either is fine.

Have fun!

Gary[/QUOTE]
I have 6 cores. However, at this point it won't be run 24/7, rather closer to 8am-12pm (16 hours a day), but still every day of the week. So those probably balance out to around a couple of months anyways.

gd_barnes 2021-04-18 21:07

I have moved the posts related to questions and answers about PRPnet and srsieve/srfile to the Software/instructions/questions thread here:
[URL]https://mersenneforum.org/showthread.php?t=9742[/URL]

pokemonlover123 2021-06-04 13:10

Update on my progress
 
I'm about halfway done with the 45G range. Unexpected gaps in being able to run the program have caused delay with making progress. However, next week I will have access to two computers that can make significant progress over that week, in addition to the one I've been using. Whether or not I reserve another range once 45G is done will depend on whether or not I have access to those PCs over the month of August, which is up in the air right now.

gd_barnes 2021-06-05 06:17

Thanks for the update.

pokemonlover123 2021-06-18 12:31

1 Attachment(s)
45G range completed to 100k
Primes attached, 1516 primes found, 1778 remain for this range.

Where do i send the residues?

rebirther 2021-06-18 17:22

[QUOTE=pokemonlover123;581330]45G range completed to 100k
Primes attached, 1516 primes found, 1778 remain for this range.

Where do i send the residues?[/QUOTE]


I have sent you a PM

pokemonlover123 2021-06-18 18:26

Residues sent.

pokemonlover123 2021-07-12 14:33

Due to extenuating circumstances, I will not have access to the 2 computers I used to quicken finishing my previous range for the month of August. I will not be reserving another range at this time, as much as I would like to.

rogue 2021-07-15 19:42

What is the status of 60G-63G?

VBCurtis 2021-07-15 22:14

60-61G is at 90k, on one core.

61-63G is distributed on a handful of cores; last I looked last week there are gaps from 65.4-70, 83-85, 88-90, 93-95, 95+. There's a core on each of those ranges, and I expect the 95+ range to finish at pretty much the same time as 60-61G.

So, about 80% done from 50k-100k.

rogue 2021-07-26 18:37

Taking 46G to 55G to n=100000. I should finish this in less than 90 days. I challenge others with R3 ranges for n < 100000 to finish before me.

rogue 2021-08-04 18:49

1 Attachment(s)
R3 46G done. Here are the primes. Residues sent to Gary.

rebirther 2021-08-07 06:37

R3 tested to n=100k (50-100k) (25-35G)

17815 remain in this range

Results emailed, Base released

rogue 2021-08-07 14:57

[QUOTE=rebirther;585048]R3 tested to n=100k (50-100k) (25-35G)

17815 remain in this range

Results emailed, Base released[/QUOTE]

Nice! The last time I looked (a few weeks ago) I was concerned that this range was falling behind and wouldn't be completed this year.

rogue 2021-08-11 16:44

1 Attachment(s)
R3 47G primes attached. Residues sent to Gary.

gd_barnes 2021-08-12 06:12

[QUOTE=rogue;585413]R3 47G primes attached. Residues sent to Gary.[/QUOTE]

You had 63 primes in this file that were duplicates. I removed them. This left 1455 unique k's with primes for the range. Can you confirm that that is what you have?

rogue 2021-08-12 13:37

[QUOTE=gd_barnes;585453]You had 63 primes in this file that were duplicates. I removed them. This left 1455 unique k's with primes for the range. Can you confirm that that is what you have?[/QUOTE]

That is correct. I'm sorry about the duplicates. The MySQL database was corrupted mid run (power outage) and I couldn't restart the MySQL service as a result. I had to re-initlialize the MySQL databsae. I reloaded the db, but couldn't easily determine which tests had to be re-run, so I went backwards a few hours from the last completed test in the logs to determine an appropriate place to start the reload. This caused a bit if retesting, but ensured that I didn't miss any primes (thus the duplicates). I was smart enough to remove the duplicates residues from the residues file.

I wonder if PostGreSQL is less susceptible to corruption. Since this is the second time this has happened to me with MySQL, it might be worth the effort to switch.

gd_barnes 2021-08-12 19:07

[QUOTE=rogue;585478]That is correct. I'm sorry about the duplicates. The MySQL database was corrupted mid run (power outage) and I couldn't restart the MySQL service as a result. I had to reinitlialize the MySQL database. I reloaded the db, but couldn't easily determine which tests had to be re-run, so I went backwards a few hours from the last completed test in the logs to determine an appropriate place to start the reload. This caused a bit if retesting, but ensured that I didn't miss any primes (thus the duplicates). I was smart enough to remove the duplicates residues from the residues file.

I wonder if PostGreSQL is less susceptible to corruption. Since this is the second time this has happened to me with MySQL, it might be worth the effort to switch.[/QUOTE]

Thanks for the info. I have also twice had to drop, create, and reload MySQL DB's due to corruption at NPLB. It is a big nuisance since I completely had to learn the process from scratch with help from others.

rogue 2021-08-12 20:07

[QUOTE=gd_barnes;585509]Thanks for the info. I have also twice had to drop, create, and reload MySQL DB's due to corruption at NPLB. It is a big nuisance since I completely had to learn the process from scratch with help from others.[/QUOTE]

If the service can start you can use mysqlcheck. I have been able to use that a couple of times.

I definitely need the spend the time to get PostgreSQL running.

rogue 2021-08-17 13:29

1 Attachment(s)
R3 48G done. Primes attached. Residues sent to Gary.

rogue 2021-08-24 14:45

1 Attachment(s)
R3 49G primes attached. Residues sent to Gary.

rogue 2021-08-30 12:02

R3 50G prime attached. Residues sent to Gary.

gd_barnes 2021-08-30 19:19

[QUOTE=rogue;586853]R3 50G prime attached. Residues sent to Gary.[/QUOTE]
No attachment.

rogue 2021-08-31 00:37

1 Attachment(s)
[QUOTE=gd_barnes;586879]No attachment.[/QUOTE]

I forgot to hit the "upload" button after choosing the file. Here they are.

rogue 2021-09-05 16:39

1 Attachment(s)
R3 51G completed. Primes attached.

rogue 2021-09-11 17:24

1 Attachment(s)
R3 52G completed. Primes attached. Residues sent to Gary.

rogue 2021-09-17 22:47

1 Attachment(s)
R3 53G completed. Primes attached. Residues sent to Gary.

rogue 2021-09-23 20:01

1 Attachment(s)
R3 54G completed. Primes attached. Residues sent to Gary.

VBCurtis has the last range of R3 to complete to complete that goal for 2021.

VBCurtis 2021-09-23 22:51

60-61G is at 93k; 61-63G has left 93-95k and 97-100k.
I believe both will finish around Halloween.

VBCurtis 2021-10-19 19:21

Progress is slower than I anticipated.
60-61G is running on 3 cores and should finish around Thanksgiving.
61-63G is running on 5 cores; the largest remaining gap is 93.5k-95k, which would take about 60 days to complete. I understand there is a goal to finish this before the end of the year, so I'll add another core to that gap to ensure I am finished with 60-63G in mid-December.

Sorry for the delay- the machine running this effort at my campus office shut down during a heat wave in early August, and I did not notice for 5 weeks. I am committed to completing these ranges on time to make the project goal.

rebirther 2021-11-11 07:17

Reserving R3 to n=1M (950k-1M) (0-2.147G) for BOINC

VBCurtis 2021-11-24 17:23

60-61G complete from 25k-100k. Primes emailed to Gary.

ETA on 61-63G is 3 weeks.

rebirther 2021-12-13 17:50

R3 tested to n=1M (950k-1M) (0-2.147G)

20 primes found, 576 remain in this range

Results emailed, Base released

VBCurtis 2021-12-16 04:43

61-63G done from 25k-100k. Primes sent to Gary, as he mentioned in the Project Goals thread.
We're done to 100k!
Time to dig out my estimate of k's remaining at 100k from like ten years ago to see how bad a forecaster I was.

VBCurtis 2022-03-07 18:38

Reserving R3 0-2.147G from 1070k to 1075k.

1000k-1070k will be sent to Reb for BOINC shortly.

I added more cores to sieving; I've used 14 threads for most of the past two months to get this piece of R3 sieved about 20% deeper. Still 16M+ candidates for 500+ k's in the sieve, so I don't think it's a candidate for Yoyo.

rebirther 2022-05-07 18:19

Reserving R3 to n=1.07M (1-1.07M) (0-2.147G) for BOINC

MisterBitcoin 2022-06-21 00:58

Reserving >63G up to n=750K.



Also considering to take a bit from n=100K-250K but only a range of 0,1G to see if I am able to quickly sieve and test it. So will only reserve it if such a small range makes sense.

rebirther 2022-06-24 20:28

R3 tested to n=1.07M (1M-1.07M) (0-2.147G)

15 primes found, 561 remain in this range

Results emailed, Base released


All times are UTC. The time now is 04:18.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2022, Jelsoft Enterprises Ltd.