Recommended bases and efforts

[gd_barnes]

Below are some recommended bases for testing.
(R=Riesel)
(S=Sierpinski)

* - fully sieved file available
p - partially sieved file available
s - sieving in progress

Sieve files can be found on our two reservations pages here:
Riesel bases
Sierpinski bases
Scroll down to the applicable base and see the file link on the far right side.

Bases with <=10000 k's remaining (at n=2500) currently at n<10K:

        # of   suggested
base     k's    search      reservation     status date
R432*   8757  n=2.5K-10K    ikari           2023/02/05
R732*   8311  n=2.5K-10K    mrlol945        2023/08/23
R822*   8895  n=2.5K-10K    pokemonlover123 2023/09/25

Bases with <=3000 k's remaining (at n=10K) currently at n<25K:

        # of   suggested
base     k's    search     reservation     status date
R388*   2747   n=10K-25K
R465*   2896   n=10K-25K
R1005*  2554   n=10K-25K
R1018*  2895   n=10K-25K
S486*   2844   n=10K-25K
S537*   2347   n=10K-25K
S540*   2632   n=10K-25K
S717*   2703   n=10K-25K
S861*   2692   n=10K-25K
S885*   2160   n=10K-25K
S975*   2920   n=10K-25K

Note: Most of the following are large efforts! Please make sure that you have the resources before reserving them.

Bases with <=20 k's remaining (at n=100K) currently at n<300K:

        # of   suggested
base     k's    search      reservation     status date
S1017*   15   n=267K-300K   dannyridel      2023/07/04

Bases < 700 with 2 k's remaining (at n=300K) currently at n<500K:

        suggested
base     search      reservation     status date
S634*  n=300K-500K   SRBase          2023/09/04
S684*  n=300K-500K   SRBase          2023/09/04

Bases < 700 with 1 k (at n=400K) remaining currently at n<600K:

        suggested
base     search      reservation     status date
(complete)

Bases < 215 with 1 k remaining (at n=600K) currently at n<1M:

        suggested
base     search      reservation     status date
R123*   n=880K-1M    bur             2023/07/17
R133*   n=950K-1M    mdettweiler     2023/09/27
R160*   n=950K-1M    mdettweiler     2023/09/27
R163*   n=950K-1M    mdettweiler     2023/09/27
R181*   n=950K-1M    mdettweiler     2023/09/27

You can post reservations and statuses in this thread but after they are done, they will be moved to their applicable threads.

[gd_barnes]

Originally Posted by Batalov

Reserving R96 as new to n=25K.

There are only 298 k's remaining after the script run at n<=1K, the results are attached. Not too shabby. Going on to n=25K.

I've just about finished taking all of those new bases to n=2500 to give people a starting point and to give a good idea of how big of an effort each would be. Yes, that was one of the better ones considering its conjecture size.

I don't know if it will help you now but attached is a file of the 176 k's remaining at n=2500 for R96.

I am now showing the # of k's remaining for each of the new bases in the 1st post at n=2500 with the exception of R108, R192, and S192 that I'm not quite done with yet. I'll attach them to the 1st post as I finish them.


Gary

[mdettweiler]

Originally Posted by gd_barnes

I've just about finished taking all of those new bases to n=2500 to give people a starting point and to give a good idea of how big of an effort each would be. Yes, that was one of the better ones considering its conjecture size.

I don't know if it will help you now but attached is a file of the 176 k's remaining at n=2500 for R96.

I am now showing the # of k's remaining for each of the new bases in the 1st post at n=2500 with the exception of R108, R192, and S192 that I'm not quite done with yet. I'll attach them to the 1st post as I finish them.


Gary

BTW, a tip for attaching files to posts such as the first post here: to attach multiple files to a single post (without having to put them all in one zip file and therefore keep re-uploading every time one little file is changed), attach the first file to the post itself; then make additional post for each respective attachment, and use the "merge posts" feature to merge them into the first post.

[gd_barnes]

Originally Posted by mdettweiler

BTW, a tip for attaching files to posts such as the first post here: to attach multiple files to a single post (without having to put them all in one zip file and therefore keep re-uploading every time one little file is changed), attach the first file to the post itself; then make additional post for each respective attachment, and use the "merge posts" feature to merge them into the first post.

Why? That would be more effort. It's easier to:

1. Add an additional file to the zip on my machine.
2. Edit the post to delete the previous attachment and add the new one.

[mdettweiler]

Originally Posted by gd_barnes

Why? That would be more effort. It's easier to:

1. Add an additional file to the zip on my machine.
2. Edit the post to delete the previous attachment and add the new one.

Well, I guess what I was thinking is if the zip file was on the largish side it would be a pain to have to upload it again each time...though I do suppose the forum's attachment size limit keeps that in check somewhat.

[gd_barnes]

Originally Posted by mdettweiler

Well, I guess what I was thinking is if the zip file was on the largish side it would be a pain to have to upload it again each time...though I do suppose the forum's attachment size limit keeps that in check somewhat.

In thinking it over a little more, I think it would be about equally fast either way. I was thinking you'd have to create a number of new posts each time that equalled the total # of files that you had. But that isn't true. For each new file, you only have to create and merge one more new post.

I'll keep that in mind for future reference since it would be slightly easier for the person who needs the info. to have them in separate files and it shouldn't be any more hassle to do it that way. Thanks for the tip.

[mdettweiler]

Originally Posted by gd_barnes

OK, I'll start sieving R181 and R182 for n=50K-100K later today. Go ahead and post a regular reservation in the bases 101-250 thread. I'll show them as reserved by you in this thread.

Great, thanks!

These bases won't keep your quad busy for very long. The natural progression of things on your effort would make S208, R214, and R221 for n=50K-100K the next ones to tackle. S208 is heavier weight so would take longer unless a prime is found quickly. Let me know if you might be interested in those.

Another thing that I'd like to see tackled is the bases <= 250 that have 2 or 3 k's remaining that are only at n=25K. There are quite a few of those. It would be nice to see if we could add them to this thread (or prove them) by knocking out a k or 2 on them. That's something I'll probably start tackling myself over the next few months if others haven't done most of them already.

To itemize those:
S72 - 2 k's remaining at 40K
S133 - 3 k's remaining at 40K
S140 - 2 k's remaining at 25K
S157 - 3 k's remaining at 25K
S187 - 2 k's remaining at 25K
S217 - 3 k's remaining at 25K
R103 - 3 k's remaining at 40K
R158 - 3 k's remaining at 25K
R191 - 2 k's remaining at 50K
R213 - 2 k's remaining at 25K
R218 - 2 k's remaining at 25K
R236 - 2 k's remaining at 25K

Heck, if my quad can burn through those 1-k-remaining bases so fast (for some reason I was initially thinking that they'd take longer--not sure why), maybe I should just go for some of those instead. Tell you what--I'll reserve R181, R182, S140, and S187 to start with, if you don't mind sieving all that. (Note that they wouldn't have to be done all at once; I imagine even one core of your i7 sieving would be enough to keep up with my quad doing PRP if you do them one at a time and send them to me as they're ready.) That should clean up all remaining unreserved bases <200 with one k remaining at 50K, and then all unreserved Sierp. bases < 250 with 2 k's remaining at 25K.

Note that in all cases, I'd be stopping at n=100K: that means 50K-100K for R181 and R182, and 25K-100K for S140 and S187.

[gd_barnes]

Originally Posted by mdettweiler

Great, thanks!


To itemize those:
S72 - 2 k's remaining at 40K
S133 - 3 k's remaining at 40K
S140 - 2 k's remaining at 25K
S157 - 3 k's remaining at 25K
S187 - 2 k's remaining at 25K
S217 - 3 k's remaining at 25K
R103 - 3 k's remaining at 40K
R158 - 3 k's remaining at 25K
R191 - 2 k's remaining at 50K
R213 - 2 k's remaining at 25K
R218 - 2 k's remaining at 25K
R236 - 2 k's remaining at 25K

Heck, if my quad can burn through those 1-k-remaining bases so fast (for some reason I was initially thinking that they'd take longer--not sure why), maybe I should just go for some of those instead. Tell you what--I'll reserve R181, R182, S140, and S187 to start with, if you don't mind sieving all that. (Note that they wouldn't have to be done all at once; I imagine even one core of your i7 sieving would be enough to keep up with my quad doing PRP if you do them one at a time and send them to me as they're ready.) That should clean up all remaining unreserved bases <200 with one k remaining at 50K, and then all unreserved Sierp. bases < 250 with 2 k's remaining at 25K.

Note that in all cases, I'd be stopping at n=100K: that means 50K-100K for R181 and R182, and 25K-100K for S140 and S187.

Sure thing. I'll just stick one core of the I7 on it in the next couple of hours. I'll see how long it takes to sieve one of them and let you know. If necessary, I might initially put a 2nd core on it to help you fill up your quad more quickly. But since sieving is only 5-10% of any total effort, 1 sieving core should well outpace 4 testing cores.

Thanks for the list. That might be a good list for others to work from also. Concentrating on bases <= 250 is good because all bases <= 250 with CK <= 10K have been or are currently being searched to n=25K. So it's virtually set in stone that there will be no more bases <= 250 with 1 or 2 k's remaining barring some miracle unknown super-heavy-weight base with CK > 10K that manages to prime all of its k's except 1 or 2. That seems virtually impossible.

BTW, I'll make a SWAG estimate at about 1-2 CPU weeks avg. on these for each k for n=50K-100K. So a quad could likely blow through them in 2-4 days each (for n=50K-100K on the 1k bases; add about 20% for each k for n=25K-100K). I think the 2 k's that I did for S218 for n=50K-100K took about 8 and 9 CPU days respectively. I ran them on one core each.


Gary

[gd_barnes]

Max,

For consistency, I added all 2k & 3k bases <= 250 that are at n<=100K. If you are going to search some 2k & 3k bases that are at 25K to 100K, then we may as well have a list of all of them that are at n<=100K. All of the others were either at 40K or 50K.

I also corrected your S133 from 25K to 40K, which prompted the additions.

The one that is "most behind" where it should be vs. its neighbors with a similar # of k's remaining is the 2 k's on S72, which are at n=40K.

BTW, all of the 1k & 2k bases that you've reserved are already recommended in this thread. These types of bases are the ones that it would be nice to have pushed higher.


Gary

[gd_barnes]

I received a sieve file from Mathew for S49 sieved to P=500G. It is now posted on the web pages.

[gd_barnes]

Originally Posted by Mathew Steine

I would like to reserve R192 to n=25K

Great! Completion of this and a few other reservations will complete all bases on both sides <=200 with CK<20K to n=25K. I think that will be a significant milestone. Many bases with CK=10K-20K have been a large amount of work to get to n=25K.

To all,

I've added a link to our 1st post in this thread to the posting that contains all bases <= 250 that have either 2 or 3 k's remaining at n<=50K. See it directly below all of the recommended bases. Max originated the post and we are working together to keep it updated. With all 1k bases <= 200 now nearly complete to n=100K, that will be a good place to look for work. Perhaps we'll end up with a few more 1k (or proven) bases. :-) Another place to look would be in the 1k thread to extend all of those bases 200-250 to n=100K.


Gary