[QUOTE=MyDogBuster;554425]Pepi, ,Could you sieve R25 n=350K--1M. Usual P

Leave out the k's over 1M[/QUOTE]

No problem
Would you like to put on the top so this sequence is first to be sieved ( if you need it quickly)?

No great hurry.

I can sieve. I participated in the Riesel search on an individual bases for quite a while. I used a combination of [I]srsieve[/I] and [I]sr1sieve[/I]. Of course, all of that was Base 2. I never tried any other bases with them. I do not see a reason why they would not work with others. I did several sieves to 5e12. If you are using [I]Yoyo[/I] then you many not need extra help. Just curious I suppose...

All help welcome. Maybe Gary (the main dude) can find something for you to do. There is plenty of sieving to do. MyDogBuster

PS: We use srsieve sr2siee here.. Sr2sieve handles multiple k's loads better that sr1siev which is good on single k

[QUOTE=MyDogBuster;554459]All help welcome. Maybe Gary (the main dude) can find something for you to do. There is plenty of sieving to do. MyDogBuster

PS: We use srsieve sr2siee here.. Sr2sieve handles multiple k's loads better that sr1siev which is good on single k[/QUOTE]

[U]Thank you for the reply[/U]. I had to do some "dusting-off" of the sieve programs since I had not used them since the end of June.

I was not aware [I]srsieve[/I] could do multiple expressions in parallel. I had never tried before. It does not appear any different when running than what I saw before. [I]sr2sieve [/I]will take some experimentation. I only used it briefly.

The way I did this before was to set everything up into a batch process which only required entering the needed parameters on a command-line. Once started, it would do everything without any extra attention from me. Basically, I didn't have to remember as much to get it going.

[QUOTE=MyDogBuster;554425]Pepi, ,Could you sieve R25 n=350K--1M. Usual P

Leave out the k's over 1M[/QUOTE]


You mean 150K not 350K?

Your correct . My 75 year old eyes failed me again.. Maybe its time for glasses. LOL

[QUOTE=MyDogBuster;554516]Your correct . My 75 year old eyes failed me again.. Maybe its time for glasses. LOL[/QUOTE]
:)
Sieve is done and sent for upload :)
This will be some kind of test since this is first base with huge number of candidates ( usually it is two to seven k)

Just will be placed as last,so it will be done in about 15-20 days

Update
Since this R25 sequence is huge and it is some kind of test for YOYO server , it is set to be first for processing: workunit are sent so first factors will be know tomorrow :)


R320
R337
R394

are finished and sent to Gary

New set of data will be sent to YOYO this weekend: if someone need to be included ( to sieve something ) can PM me.
R25 is nearly done, we have 19 MB of factors ( for now) or 571723 factors found ( for now)

Few sieve is done and sent to Gary
R25
S365
S444
S447

New sieve batch will be sent to YOYO in few days. If some need some sieve, now is time :)
You can leave post here or on PM

[QUOTE=pepi37;558399]New sieve batch will be sent to YOYO in few days. If some need some sieve, now is time :)
You can leave post here or on PM[/QUOTE]


Do we have already the rest of all recommended bases sieve files in pipeline?

[QUOTE=rebirther;558717]Do we have already the rest of all recommended bases sieve files in pipeline?[/QUOTE]
No , but we will have it: since nobody ask nothing: rest of recommended bases is priority one!

r_602
r_643
r_667
r_694
r_696
r_803
r_887
r_1003
sent for sieving

New set of data will be sent to Yoyo!
Does anyone has any "sieve wish"? :)

[QUOTE=pepi37;562127]New set of data will be sent to Yoyo!
Does anyone has any "sieve wish"? :)[/QUOTE]


R107, S368, S994 :-)

R15 (10M-20M) n=25-100k

Today I and YOYO will try our deepest sieve file ( and as such) we will pass our previous record of 20000 WU per sieve files. I test in on my two repdigit sequences. So if all be ok, new sieve depth can be 15e16


This will be[I][U][B] used only on NPG files ( base with one K remain) [/B][/U][/I]since in that case one workunit is 500e9.


I will inform you in progress. Best regards to all

[QUOTE=sweety439;567491]You can sieve the 1k bases at n<1M with no sieve file to 1M: (see [URL]https://mersenneforum.org/showthread.php?t=12980[/URL]), they are:

S117 500K-1M
S257 600K-1M
S430 500K-1M
S497 500K-1M
S789 500K-1M
S883 500K-1M
R883 500K-1M
R968 500K-1M[/QUOTE]


I can always sent those base for sieving, but until now I was limited to 1e15. So we now extended , but easy ,step by step.We can be sure YOYO system can handle without problem 40000 workunits per sequence

[QUOTE=pepi37;567492]I can always sent those base for sieving, but until now I was limited to 1e15. So we now extended , but easy ,step by step.We can be sure YOYO system can handle without problem 40000 workunits per sequence[/QUOTE]

Please do not listen to Sweety. He trolls here constantly and is not part of this project. He does not understand anything about work effort required because he never does any work for the project. The sieve depth that you are discussing is great but it would be much better done for sequences where n>1M. It would be a waste of sieving effort for n<1M.

One of our main goals for 2021 will be testing all bases with 9 or 10 k's remaining to n=200K. So if you can pick out some of those bases that are only tested to n=100K and sieve them for n=100K-500K that would be more helpful for the project.

In the next few days I will be posting our goals for 2021.

@Gary and @Pepi
 

Just a lot of rambeling, did not understand that there was no need for initial sieving. :smile:

Happy new year :smile:

[QUOTE=KEP;567526]Hi :smile:

I've come to a point, where P95 and LLR work is no longer possible on my i5 4670, but it shows no signs of trouble when sieving and since sieving is less stressfull on the CPU, I'm going to retire the i5 4670 from LLR and devote it to sieving. In regards to my reservation on SR383 it will be completed, since I'm going to build 2 systems with Ryzen 9 3900X processor, wich will start out by doing about 1000 tests a day on S383 - so what would have been a delay has now forced me to upgrade to a scale where 20 times as much work can be done each day and to an extent such that maybe 2 primes for S383 is possible next year, even if I double check some or all of my completed work for S383 (work not already double checked by PG).

Now back to the offer of sieving, I have 4 cores, so can you give me 4 bases to sieve for n=100K to n=500K or to n=1M(?)?

I'm very late for this party, but are these following bases tested to n100K and with 9 k's remaining available for sieving:

S572 to n=500K or n=1M?
S639 to n=500K or n=1M?
S908 to n=500K or n=1M?
S977 to n=500K or n=1M?

How deep do I have to sieve, before sending to Pepi and Pepi sending to YOYO?

Thanks for any guidelines and if those above is not available please give me 4 different bases :smile:

Take care[/QUOTE]


KEP you dont need to donate your CPU for sieving: I made all: initial sieve before I sent to YOYO is done in minutes, and then it is sent to YOYO to finish. So use your CPU for you : every processed workunit is one less :)
Thanks for offering your computer power :)

I can provide the following bases for deeper sieving:


R709, 100K-250K

R711, 100K-250K
R798, 200K-500K
R806, 400K-1M
R1017, 250K-500K

[QUOTE=MisterBitcoin;567769]I can provide the following bases for deeper sieving:


R709, 100K-250K

R711, 100K-250K
R798, 200K-500K
R806, 400K-1M
R1017, 250K-500K[/QUOTE]

The deeper sieve depth that Pepi is referring to should only be used for n>1M. It would be a waste of resources to sieve smaller tests to such a depth.

It's no big deal if Pepi has Yoyo sieve these. But I suggest sieving them to their usual depth that they have always done, not the deeper depth.

[QUOTE=gd_barnes;567800]The deeper sieve depth that Pepi is referring to should only be used for n>1M. It would be a waste of resources to sieve smaller tests to such a depth.

It's no big deal if Pepi has Yoyo sieve these. But I suggest sieving them to their usual depth that they have always done, not the deeper depth.[/QUOTE]


Those are sieved up to 25e9 and one up to 50e9 and would recommend to sieve them deeper with yoyo@home.

50e12 sounds like a fair value for them.

All is OK, I will made and sent to YOYO all sieves: for him it is irrelevant how deep is initial sieve.

Goal 4 is an large amount of work.
I am not sure if srsieve2 can handle that large k. (srsieve could, but its very slow)

Other than that i am willing to help sieving on R3.



According to the Remain side "only" 35G-55G is left, or do you already have an sieve file for that range?




Other than that i dont thing i cant contribute that much this year. Main focus for me is NF@home.

[QUOTE=MisterBitcoin;567942]Goal 4 is an large amount of work.
I am not sure if srsieve2 can handle that large k. (srsieve could, but its very slow)

Other than that i am willing to help sieving on R3.

According to the Remain side "only" 35G-55G is left, or do you already have an sieve file for that range?

Other than that i dont thing i cant contribute that much this year. Main focus for me is NF@home.[/QUOTE]

I would be surprised if srsieve2 could not. Assuming it does, due to the most recent changes in srsieve2, I cannot think of any case where srsieve2 is slower than srsieve.

I'll give it a spin and let you know what happens.

Seems to work fine with all remaining k between 25G and 60G:

[code]srsieve2 -P1e9 -n5e4 -N1e5 -sr3.in -W6
srsieve2 v1.3, a program to find factors of k*b^n+c numbers for fixed b and variable k and n
(kp) Sequence has algebraic factorization: 46908629056*3^n-1 -> (216584^2)*3^n-1
(kp) Sequence 46908629056*3^n-1 has 25001 terms removed due to algebraic factors of the form 216584*3^(n/2)-1
Sieving with generic logic
Sieve started: 3 < p < 1e9 with 4944273883 terms (50000 < n < 100000, k*3^n+c) (expecting 4682160754 factors)
p=1213, 0.656 p/sec, 4560646177 factors found at 262.5K f/sec (last 1 min), 0.0% done. ETC 2097-09-06 18:43
Sieving with generic logic
Split 98884 base 3 sequences into 98884 base 3^1 sequences.
p=1571749, 304.1 p/sec, 4758573825 factors found at 2.019K f/sec (last 1 min), 0.2% done. ETC 2021-02-24 07:05
[/code]

The ETC is is off because of factor validation. As the factor density decreases, the ETC will become more accurate as the p/sec will increase.

srsieve2 with 6 threads is taking about 2G of memory. The ABCD file is less than 700M

I will let this run longer, but I'm not certain that I will finish the sieving to 1e9.

[QUOTE=MisterBitcoin;567942]According to the Remain side "only" 35G-55G is left, or do you already have an sieve file for that range?[/QUOTE]

Yes, there is a sievefile ready, made by Gary and seems to have been taken up partially or fully by BOINC. Currently srbase is working on 25G-35G, as I remember it, from n>50K to n=100K.

I fooled around recently, when getting familiar with srsieve2, trying to sieve ALL k's remaining for S3 - none of them failed to sieve. To be honest I would be surprised, if any of our current confined amount of conjectures has k's that fail to be able to be sieved - the only possible conjecture for reaching a limitation of k, could and would only be R280 - but it is not gonna be started for many years, so it is - if it should be a concern - not really a current concern :smile:

[QUOTE=rogue;567957]Seems to work fine with all remaining k between 25G and 60G:

[code]srsieve2 -P1e9 -n5e4 -N1e5 -sr3.in -W6
srsieve2 v1.3, a program to find factors of k*b^n+c numbers for fixed b and variable k and n
(kp) Sequence has algebraic factorization: 46908629056*3^n-1 -> (216584^2)*3^n-1
(kp) Sequence 46908629056*3^n-1 has 25001 terms removed due to algebraic factors of the form 216584*3^(n/2)-1
Sieving with generic logic
Sieve started: 3 < p < 1e9 with 4944273883 terms (50000 < n < 100000, k*3^n+c) (expecting 4682160754 factors)
p=1213, 0.656 p/sec, 4560646177 factors found at 262.5K f/sec (last 1 min), 0.0% done. ETC 2097-09-06 18:43
Sieving with generic logic
Split 98884 base 3 sequences into 98884 base 3^1 sequences.
p=1571749, 304.1 p/sec, 4758573825 factors found at 2.019K f/sec (last 1 min), 0.2% done. ETC 2021-02-24 07:05
[/code]

The ETC is is off because of factor validation. As the factor density decreases, the ETC will become more accurate as the p/sec will increase.

srsieve2 with 6 threads is taking about 2G of memory. The ABCD file is less than 700M

I will let this run longer, but I'm not certain that I will finish the sieving to 1e9.[/QUOTE]

I have issues with the boinc output file. With -W16 it has stopped at 32M of 1G and with -W30 it had a massive slowdown (sieving around 320k factors), the outputfile was 2.5GB and had 162M lines. I have 128GB so memory should not be a problem.

[QUOTE=rebirther;567963]I have issues with the boinc output file. With -W16 it has stopped at 32M of 1G and with -W30 it had a massive slowdown (sieving around 320k factors), the outputfile was 2.5GB and had 162M lines. I have 128GB so memory should not be a problem.[/QUOTE]

This occurs because the program is waiting for all workers to finish before it can be guaranteed there are no unsieved gaps below the p in the output file.

There are two options. One use a smaller -w so that the threads have less work per iteration. The other is to rename the output file from the previous checkpoint and hit ^C twice.

R3 is already fully sieved by me. Otherwise I would not have made it a goal.

I used srsieve. It worked well. It was easy enough to split the sieve into multiple k-ranges and then combine them all at the end.

Running multiple instances of srsieve seemed much faster than srsieve2.

Since R3 sieve is done, i would start with sieving existing sieve files deeper for n=2,5K-10K. If i havent counted wrong those are 66 bases for the Riesel side alone. (and 49 on Sierp-side)

[QUOTE=MisterBitcoin;567982]Since R3 sieve is done, i would start with sieving existing sieve files deeper for n=2,5K-10K. If i havent counted wrong those are 66 bases for the Riesel side alone. (and 49 on Sierp-side)[/QUOTE]

Optimum sieve depth on those averages P=~15G and they are currently only at P=1G. That is a serious effort for most folks, even for just sieving. Yoyo cannot do them because it's too many k's.

You definitely want to only take one at a time. :-)

[QUOTE=gd_barnes;567986]Optimum sieve depth on those averages P=~15G and they are currently only at P=1G. That is a serious effort for most folks, even for just sieving. Yoyo cannot do them because it's too many k's.

You definitely want to only take one at a time. :-)[/QUOTE]


I just started with R1012, my speed is at 270p/sec using 4 threads. So yeah, its slow.

However in a few days my new 10-Core i9 will arrive, so i should get some speed-up^^

Gary, what is your opinion on spliting larger bases, lets say more than 10K k´s, into smaller files. Example:

2,5K up to 4K
4K up to 7,5K
7,5K up to 10K.



That way should make it a bit easier to sieve deeper for the 2nd and 3th stage due to the removed k´s. :smile:
(Granted, thats more effort from your, Reb´s and my side)

[QUOTE=MisterBitcoin;567996]Gary, what is your opinion on spliting larger bases, lets say more than 10K k´s, into smaller files. Example:

2,5K up to 4K
4K up to 7,5K
7,5K up to 10K.



That way should make it a bit easier to sieve deeper for the 2nd and 3th stage due to the removed k´s. :smile:
(Granted, thats more effort from your, Reb´s and my side)[/QUOTE]

I will be using 10k factors per core next time but running 30 instances on 16core.

[QUOTE=MisterBitcoin;567996]Gary, what is your opinion on spliting larger bases, lets say more than 10K k´s, into smaller files. Example:

2,5K up to 4K
4K up to 7,5K
7,5K up to 10K.



That way should make it a bit easier to sieve deeper for the 2nd and 3th stage due to the removed k´s. :smile:
(Granted, thats more effort from your, Reb´s and my side)[/QUOTE]

If I was going to split n=2.5K-10K by n-value, if would be in two: n=2.5K-5K and n=5K-10K. Splitting more than that saves so little CPU effort that it is not worth the manual effort to do so.

But...the tests are so fast for n=2.5K-10K that I just prefer to split them up by k-value and sieve the entire n-range to the same depth.

For instance I sieved the 320,000+ k's for R271 by splitting it up into 20 instances of ~16,000 k's each and sieving all of n=2.5K-10K to P=1G. That is not nearly deep enough for testing but the files on the pages are intended to be a starting point for others to sieve deeper before beginning testing. Optimum depth for the typical base for the entire k-range and n=2.5K-10K is P=~10G to 15G. If I am personally testing them I'll just sieve the whole thing to P=15G.

[QUOTE=gd_barnes;568046]If I was going to split n=2.5K-10K by n-value, if would be in two: n=2.5K-5K and n=5K-10K. Splitting more than that saves so little CPU effort that it is not worth the manual effort to do so.

But...the tests are so fast for n=2.5K-10K that I just prefer to split them up by k-value and sieve the entire n-range to the same depth.

For instance I sieved the 320,000+ k's for R271 by splitting it up into 20 instances of ~16,000 k's each and sieving all of n=2.5K-10K to P=1G. That is not nearly deep enough for testing but the files on the pages are intended to be a starting point for others to sieve deeper before beginning testing. Optimum depth for the typical base for the entire k-range and n=2.5K-10K is P=~10G to 15G. If I am personally testing them I'll just sieve the whole thing to P=15G.[/QUOTE]

I would be curious to see some statistics comparing the speed of srsieve to srsieve2 for these ranges. How you split n or k is up to you for that comparison.

Ok i have an short update about R1012. I started the process early this morning on one of my servers, after around 15 hours i found ~600.000 factors.
Earlier it showed to reach 5e9 on the 28.01, now it will reach this in about 24 hours.


I think its safe to say its ready for n=2,5K-5K by tomorrow.

Also i finished R1005, at around 12e9 it surpassed the average LLR runtime by ~20%. Should be enough to get tested by BOINC. Should i send the file to reb or Gary?

[QUOTE=MisterBitcoin;568097]Ok i have an short update about R1012. I started the process early this morning on one of my servers, after around 15 hours i found ~600.000 factors.
Earlier it showed to reach 5e9 on the 28.01, now it will reach this in about 24 hours.


I think its safe to say its ready for n=2,5K-5K by tomorrow.

Also i finished R1005, at around 12e9 it surpassed the average LLR runtime by ~20%. Should be enough to get tested by BOINC. Should i send the file to reb or Gary?[/QUOTE]

Please wait to send me R1012 until you are done with the entire n-range. There is no reason to send me pieces. For such small tests it would be easier if the entire n-range was sieved to the same depth even if it means a little more CPU time in the long run. It's easier to set it and forget it until it is done, both for sieving and testing.

For R1005, BOINC does not run such small tests. You can send me the sieve file. I will post it on the page. Others can reserve it if they want although I doubt it will get much interest for such a large base and large # of k's remaining. Anything with over 10,000 k's remaining is an extremely large effort to fully test. Even over 5,000 k's is big.

[QUOTE=gd_barnes;568101]Please wait to send me R1012 until you are done with the entire n-range. There is no reason to send me pieces. For such small tests it would be easier if the entire n-range was sieved to the same depth even if it means a little more CPU time in the long run. It's easier to set it and forget it until it is done, both for sieving and testing.

For R1005, BOINC does not run such small tests. You can send me the sieve file. I will post it on the page. Others can reserve it if they want although I doubt it will get much interest for such a large base and large # of k's remaining. Anything with over 10,000 k's remaining is an extremely large effort to fully test. Even over 5,000 k's is big.[/QUOTE]




Sieving R1012 up to P=15e9 shouldn´t take much longer, expecting it to finish in about 6-7 days before taking the next file.

R1005 sieve file will be added in the thread shortly.

R1012 reached p=15e9 at a speed of 5,77 secs/factor. The sieve file has been send via PM to Gary.



Next file taken for sieving is R375.

R375 sieve file reached P=15e9 and is at 4,2 secs/factor (using 8 cores), file attached.


Now taking R970.

R970 reached P=15e9 at a speed of 4,14 secs/factor (8 cores); file attached.


Now taking R250.

R250 reached p=15e9 at a speed of 4,72 sec/fac (using 8 cores), file attached.



Taking R955, R933, R913 and R885 as next.

R885 reached P=15e9, file attached.

Sieve files for R913, R933 and R955 can be found [URL="https://mega.nz/file/fOxmRQDZ#gvYwR6nIo7h5lsMPlvGoHEmslop2dEF9FFwZPO9YsMk"]here[/URL]


I am still considering to get an GPU server to handle the sieve files even faster, with an additional deeper test limit too.



For now I am taking R586 and will sieve it to around 20e9. It should take longer due to its massive amount of k´s.

[QUOTE=MisterBitcoin;569844]
For now I am taking R586 and will sieve it to around 20e9. It should take longer due to its massive amount of k´s.[/QUOTE]


R586 reached ~19,8B which an factor rate of 6,42 secs per factor; you can find it [URL="https://mega.nz/file/nWp22SiD#jIZm3NEifFTecbTeCyJoLidxnPMMoRKqXT37buej-sk"]here[/URL]


I have done quite a few for the Riesel side, now doing a few on the Sierpinski side:
S990
S975
S970
S885
S861
S786
S775

First 5 files reached P=15e9, see attachments.

Pepi,

After the current batch of files for sieving base 2 is done, please refer to the following post as our next priority for sieving:

[URL]https://mersenneforum.org/showpost.php?p=209366&postcount=1[/URL]

Please have them sieved for n=100K-500K (or n=200K-500K).

The Riesel bases with 9 or 10 k's remaining for n=100K-500K are the higher priority.

Thanks! :-)

Gary

[QUOTE=gd_barnes;574604]Pepi,

After the current batch of files for sieving base 2 is done, please refer to the following post as our next priority for sieving:

[URL]https://mersenneforum.org/showpost.php?p=209366&postcount=1[/URL]

Please have them sieved for n=100K-500K (or n=200K-500K).

The Riesel bases with 9 or 10 k's remaining for n=100K-500K are the higher priority.

Thanks! :-)

Gary[/QUOTE]


Will be done!

First batch is sent for sieving


sr_529.abcd
sr_572.abcd
sr_639.abcd
sr_698.abcd
sr_908.abcd

sieving S357 to 10e9

S357 sieved to 10G


Results emailed