R1019 has been sieved up to p=1e15. Factors checked, file attached.

[QUOTE=MisterBitcoin;470107]R1019 has been sieved up to p=1e15. Factors checked, file attached.[/QUOTE]

Nice sieve depth! :smile:

[QUOTE=MisterBitcoin;470096]The BOINC software is checking if all results from the WU´s are comming back or not.

The WU-Generator generates ~10.000 WUs with each 2 Tasks/WU. The software checks if all Tasks are comming back in time, if not new tasks will be generated and sended.

It´s all automatic, like srbase. The software behind it is the same, it´s only speciefied.[/QUOTE]

OK but I am still confused on how you posted a file and then found that additional factors had been found so that you had to post another file.

In the future, I will assume that you will only post [B]fully[/B] sieved files when you know that all factors have been reported.

So, here he go.
Sieve app passed 8 CPU years!

4 sieve files attached, P-Values below.

R103: 300e12
R368: 500e12
R1024: 1e15
R1029: 1e15

I´m now running stuff for Pepi and Masser. Curtis, if you need deeper sieve files feel free to PM me.

S497 reached p = 40T, sieve file is attached below.

Some information on expected primes for this file:
[CODE]expected # of primes: 0.13649300098661327
odds of at least one prime: 12.758757373549578%
(or, in other words) 1 in 7.837753871494719 chance of at least one prime
on average, 1 in 36338.85960560321 candidates should be prime[/CODE]

Reserving S61 for sieving, n = 100k to n = 250k.

Hi!
If i want to reserve and sieve S476, which settings in sr1sieve i must set and how long i must sieve?
Pre-thanks
P.S
I already sieved up to 1e9 in srsieve.

Reserving all single-k bases on Sierpinski-Side without sieve file. That should be ~48 bases.
We need ~1,5 days/sequence. I´m now preparing the bases that are suggested by Gary.

Sorry vasyannyasha, there is no need to sieve S476. Please check Riesel side for an single-k base without sieve file.

@Gary Sorry that this goes so fast. Since I´m on night shift I haven´t enough time to post an reservation on the following bases:

R968 from n=250K-500K; P=250e12
R888 from n=400K-1M; P=750e12
R883 from n=250K-500K; P=250e12
R995 from n=500K-1M; P=500e12

All 4 attached.

Reserving S290 from n=100K-250K. k=73 has only ~1800 tests on p=5e9.

It´s going forward, once again a few from Riesel side.

Attached are:

R905; 400K-1M; P=750e12
R951, 200K-500K, P=250e12
R879, 200K-500K, P=250e12

One more done, S290 reached p=250e12, file attached

Yes, that P is a bit too large. :D

3 more done.

S128, n=1.28-3M, P=1e15.
S112, n=1-3M, P=1e15
S200, n=1-3M, P=1e15

Nice work on the sieving.

Suggestions for sieving from the recommended bases thread:
R398 n=200K-500K
R615 n=100K-250K
R643 n=100K-250K
R662 n=200K-500K
S376 n=100K-250K
S392 n=100K-250K
S412 n=100K-250K
S447 n=100K-250K
S550 n=200K-500K

[QUOTE=gd_barnes;472342]Nice work on the sieving.

Suggestions for sieving from the recommended bases thread:
R398 n=200K-500K
R615 n=100K-250K
R643 n=100K-250K
R662 n=200K-500K
S376 n=100K-250K
S392 n=100K-250K
S412 n=100K-250K
S447 n=100K-250K
S550 n=200K-500K[/QUOTE]

As stated all single-k´s without sieve file are running now, after they are finished I´ll start working on the recommended bases.

[QUOTE=MisterBitcoin;472343]As stated[/QUOTE]

As stated where? lol

That's 50-100 or more sieve files. Are you really sieving ALL one k bases without sieve files?

[QUOTE=MisterBitcoin;471665]Reserving all single-k bases on Sierpinski-Side without sieve file. That should be ~48 bases.
We need ~1,5 days/sequence. I´m now preparing the bases that are suggested by Gary.
.[/QUOTE]

There. :)
I´m sure I got all single-k bases without sieve files on Sierpinski, but I´ll check when all file are completed. :smile:

[QUOTE=MisterBitcoin;472385]There. :)
I´m sure I got all single-k bases without sieve files on Sierpinski, but I´ll check when all file are completed. :smile:[/QUOTE]

Ah. I missed that part. :-) A suggestion would be to first sieve the 1k bases that are only tested to n=200K so far. There will be some fast proofs in those. The ones that are already tested to n=1M take an extraordinary amount of time to test.

R622
 

I want to reserve R622.
Pre-thanks

R1027 has reached p=15e12, file attached.

Huge update today.
I was waiting a few weeks to gain a good amount of files done by yoyo@home.
Here we go:

S43, n=1M-3M, P=1e15
S227, n=1M-3M, P=1e15
S294, n=200K-1M, P=500e12
S304, n=1M-3M, P=1e15
S340, n=400K-1M, P=750e12
S379, n=200K-1M, P=500e12
S426, n=400K-1M, P=750e12
S436, n=400K-1M, P=750e12
S450, n=400K-1M, P=750e12
S461, n=250K-1M, P=750e12
S476, n=200K-1M, P=750e12
S480, n=200K-1M, P=750e12
S492, n=400K-1M, P=1e15 (recommended due to low nash, 6975 tests)
S512, n=1M-3M, P=1e15
S516, n=200K-1M, P=750e12
S534, n=200K-1M, P=750e12
S550, n=200K-1M, P=750e12
S574, n=200K-1M, P=750e12
S582, n=200K-1M, P=750e12
S605, n=200K-1M, P=750e12
S638, n=400K-1M, P=750e12
S649, n=200K-1M, P=750e12
S676, n=400K-1M, P=750e12
S678, n=500K-1M, P=750e12
S702, n=200K-1M, P=750e12
S707, n=200K-1M, P=750e12
S720, n=200K-1M, P=750e12
S724, n=200K-1M, P=750e12
S736, n=200K-1M, P=750e12

That's a large amount of work. :smile:
Even if I´m (at least) 1 day too early: Merry Christmas. [Why don´t we have a Christmas smile?]

[QUOTE=MisterBitcoin;474736]Huge update today.
I was waiting a few weeks to gain a good amount of files done by yoyo@home.
Here we go:
<snip>
[/QUOTE]

Wow... You will reserve ALL 1k Sierpinski bases b<=512 to n=1M!!!

Nice work coordinating all of that MisterBitcoin. :smile:

[QUOTE=MisterBitcoin;474736]Huge update today.
I was waiting a few weeks to gain a good amount of files done by yoyo@home.
Here we go:

S43, n=1M-3M, P=1e15
S227, n=1M-3M, P=1e15
S294, n=200K-1M, P=500e12
S304, n=1M-3M, P=1e15
S340, n=400K-1M, P=750e12
S379, n=200K-1M, P=500e12
S426, n=400K-1M, P=750e12
S436, n=400K-1M, P=750e12
S450, n=400K-1M, P=750e12
S461, n=250K-1M, P=750e12
S476, n=200K-1M, P=750e12
S480, n=200K-1M, P=750e12
S492, n=400K-1M, P=1e15 (recommended due to low nash, 6975 tests)
S512, n=1M-3M, P=1e15
S516, n=200K-1M, P=750e12
S534, n=200K-1M, P=750e12
S550, n=200K-1M, P=750e12
S574, n=200K-1M, P=750e12
S582, n=200K-1M, P=750e12
S605, n=200K-1M, P=750e12
S638, n=400K-1M, P=750e12
S649, n=200K-1M, P=750e12
S676, n=400K-1M, P=750e12
S678, n=500K-1M, P=750e12
S702, n=200K-1M, P=750e12
S707, n=200K-1M, P=750e12
S720, n=200K-1M, P=750e12
S724, n=200K-1M, P=750e12
S736, n=200K-1M, P=750e12

That's a large amount of work. :smile:
Even if I´m (at least) 1 day too early: Merry Christmas. [Why don´t we have a Christmas smile?][/QUOTE]

@Gary, you miss the sieve file of S476 in [URL="http://www.noprimeleftbehind.net/crus/Sierp-conjecture-reserves.htm"]http://www.noprimeleftbehind.net/crus/Sierp-conjecture-reserves.htm[/URL]

R-500
 

Here is R500 k= 38,53,82 from 250K -500K
Sieve depth is 13400000000000

Reserving R662 and R398 for sieving n=200K-500K.

@Gary
Can you zip the remain k´s for all bases tested up to n=10K with less than 1,000 k´s?
Those bases should be R606, R877, R996, S606, S807 and S1005.
I´ll sieve them up to n=25K.

I´m also working on the sieve files done my yoyo@home, maybe I´ll upload them in the middle of the night or tomorrow.

[QUOTE=MisterBitcoin;476718]@Gary
Can you zip the remain k´s for all bases tested up to n=10K with less than 1,000 k´s?
Those bases should be R606, R877, R996, S606, S807 and S1005.
I´ll sieve them up to n=25K.

I´m also working on the sieve files done my yoyo@home, maybe I´ll upload them in the middle of the night or tomorrow.[/QUOTE]

Here ya go.

I have finished sieving R662 for n=200K-500K to P=55T. I have added it as a recommended base for BOINC.

Next update on Sierpinski-Single k and recommended bases for Riesel and Sierpinski.

S740, 200K-1M, p=750e12
S743, 200K-1M, p=750e12
S758, 500K-1M, p=750e12 (4728 terms)
S778, 200K-1M, p=750e12
S780, 200K-1M, p=750e12
S781, 200K-1M, p=750e12
S785, 400K-1M, p=750e12 (4593 terms)
S798, 200K-1M, p=750e12
S806, 400K-1M, p=750e12
S816, 200K-1M, p=750e12
S828, 500K-1M, p=750e12 (6362 terms)
S834, 400K-1M, p=750e12
S836, 200K-1M, p=750e12
S864, 500K-1M, p=750e12

Quite much work. I missed some bases, like S9. When those sequences are listed on the page I´ll make an audit and generate new input files for single-k´s.
For now I´m switching to Riesel, there is a large amount of sieving work to do.

Some more work:

S376, 100K-250K, P=100e12
S392, 100K-250K, P=100e12
S412, 100K-250K, P=100e12
S447, 100K-250K, P=100e12
R615, 100K-250K, P=100e12

BASE 53 -remain K
 

Since YOYO need urgent more work -queue was empty: I send him all remain K on base 53 from 100K to 1M
That will give him work for at least 10-15 days so you have plenty of time to prepare new work in meantime
K are 152,184,280,346,544,866,872,1066,1084,1154,1174,1238,1298,1328,1414,1426,1534,1838,1862 and 1892

[QUOTE=pepi37;476852]Since YOYO need urgent more work -queue was empty: I send him all remain K on base 53 from 100K to 1M
That will give him work for at least 10-15 days so you have plenty of time to prepare new work in meantime
K are 152,184,280,346,544,866,872,1066,1084,1154,1174,1238,1298,1328,1414,1426,1534,1838,1862 and 1892[/QUOTE]

S53, to be detailed. :smile:

And it looks like sr2sieve is alive on YOYO. So prepare work for sieving :)

[QUOTE=pepi37;477575]And it looks like sr2sieve is alive on YOYO. So prepare work for sieving :)[/QUOTE]

:grin:

Bring on some of those 2, 3, and 4k bases for n=100K-250K! :smile:

For non-overlap other sieving process ( and we still have few days to prepare more work) please, write what exactly base you should recommend ( and of course recommended sieve depth)
Then I will in next post here write what bases are sent to YOYO.
Thanks

[QUOTE=pepi37;477622]For non-overlap other sieving process ( and we still have few days to prepare more work) please, write what exactly base you should recommend ( and of course recommended sieve depth)
Then I will in next post here write what bases are sent to YOYO.
Thanks[/QUOTE]

I think we should aim for bases <10 k´s remain now. This should take some time.
I´ll take care on the sierpinski-side and, if you want, you can take the Riesel side.

[QUOTE=MisterBitcoin;477635]I think we should aim for bases <10 k´s remain now. This should take some time.
I´ll take care on the sierpinski-side and, if you want, you can take the Riesel side.[/QUOTE]

My suggestion would be to start with bases that have 2, 3, and 4 k's remaining that are currently searched to n=100K since that is a major project goal. Do all of those first and then do the bases with 5-10 k's remaining.

My suggestion is to do the n=100K-250K range to begin with.

Following your suggestion next bases are sent to YOYO
R281
R338
R370
R380
R410
R447
R452
R516
R526
R530
R532
R579
Range is from 100K to 300K pmax =50e12

Nobody have those bases reserved, so I assume they are free , and since noone has no sieve files... it was my choice

Sieve file for R996 reached 75,9G.
File attached.

I have finished sieving R398 for n=200K-500K to P=60T. It is on the recommended bases list.

Next one done.
R643 (n=100K-250K) reached P=100e12.

Reserving all Riesel single-k bases for yoyo@home.
Also reserving S263 from n=1M-3M for yoyo@home.

[QUOTE=MisterBitcoin;478274]Reserving all Riesel single-k bases for yoyo@home.
Also reserving S263 from n=1M-3M for yoyo@home.[/QUOTE]

Great! Based on this the first post in this thread is becoming too cumbersome for me to continue updating. Sometime on Friday I will remove all of the sieving reservations and completions there and refer everyone to posts in this thread as well as already sieved files on the reservations pages.

MisterBitcoin, I have completed R411 to n=25K. With 182 k's remaining, there are fewer remaining than any other base currently tested to only n=25K. I have started a sieve for n=25K-100K to a very small sieve depth of P=1G. The file is attached in ABCD format. Can you have Yoyo sieve it to some reasonable depth so that BOINC can eventually test it? Thanks. :smile:

[QUOTE=gd_barnes;478695]MisterBitcoin, I have completed R411 to n=25K. With 182 k's remaining, there are fewer remaining than any other base currently tested to only n=25K. I have started a sieve for n=25K-100K to a very small sieve depth of P=1G. The file is attached in ABCD format. Can you have Yoyo sieve it to some reasonable depth so that BOINC can eventually test it? Thanks. :smile:[/QUOTE]
Pmax is set to 10e13 and it is sent to YOYO. But dont expect it before one month:since there is 92 sequences in queue now :smile:

[URL]http://www.rechenkraft.net/yoyo/y_status_sieve.php[/URL]

[QUOTE=pepi37;478746]Pmax is set to 10e13 and it is sent to YOYO. But dont expect it before one month:since there is 92 sequences in queue now :smile:

[URL]http://www.rechenkraft.net/yoyo/y_status_sieve.php[/URL][/QUOTE]

OK thanks. That is fine. By the way, when you say 10e13, do you mean 1e13 or 1e14? Either one is good with me.

[QUOTE=gd_barnes;478752]OK thanks. That is fine. By the way, when you say 10e13, do you mean 1e13 or 1e14? Either one is good with me.[/QUOTE]

I´ve told yoyo to not put it into the queue now, it is only tested up to 1G!
I will sieve it to an other P-value in order to prevent yoyo@Home users from extreme long running WU´s.
More tests means more runtime, thats why R2 took over 1 day at ARM!

[QUOTE=MisterBitcoin;478782]I´ve told yoyo to not put it into the queue now, it is only tested up to 1G!
I will sieve it to an other P-value in order to prevent yoyo@Home users from extreme long running WU´s.
More tests means more runtime, thats why R2 took over 1 day at ARM![/QUOTE]

ARM?
You cannot stop users to use weak CPU, and ARM is weak, extremely weak compared to any modern CPU. Butt, those kind of members is also in very low number compared to all other users that do sieving. And last: if WU is not return in deadline it recycled immediately. So dont stop project because few users.

[QUOTE=pepi37;478783]ARM?
You cannot stop users to use weak CPU, and ARM is weak, extremely weak compared to any modern CPU. Butt, those kind of members is also in very low number compared to all other users that do sieving. And last: if WU is not return in deadline it recycled immediately. So dont stop project because few users.[/QUOTE]

Those tasks can, and will, run way faster if I remove more canidates NOW.
ARM was an examble. Try it out: Run 12T up to 12,05T with an version removed canidates from 1G up to 50G and an version without removed canidates from that range.
There will be an noticeable speed-up from about 10-15%! :smile:
(That counts for all types of CPUs anyway.)

My apologies. Yes that was a quick sieve to P=1G. I could have easily sieved it to P=10G (Would that be enough?) but I just figured that Yoyo could do it a lot faster. I also could have just handed over a k's remaining file to you and suggested that you do the initial sieve. I guess I found the worst way in between the two extremes. :-(

Since I'll likely have a few more of these this year, in the future for an n=25K-100K file, what depth should I sieve it to for Yoyo to get started on it? Or would you prefer that I just post a k's remaining file and have you take it from there?

[QUOTE=gd_barnes;478798]My apologies. Yes that was a quick sieve to P=1G. I could have easily sieved it to P=10G (Would that be enough?) but I just figured that Yoyo could do it a lot faster. I also could have just handed over a k's remaining file to you and suggested that you do the initial sieve. I guess I found the worst way in between the two extremes. :-(

Since I'll likely have a few more of these this year, in the future for an n=25K-100K file, what depth should I sieve it to for Yoyo to get started on it? Or would you prefer that I just post a k's remaining file and have you take it from there?[/QUOTE]

It´s okay. I started the sieving right after I noticed your post yesterday. I´ll sieve it to 150G, since yoyo@home has an quite large queue.
There is also no experience with so much k´s for yoyo with sr2sieve. I want to be 100% sure that this implementation works without any problems.

For the future you can also upload the files on the RKN slack "sieving" thread, I´ll take them deeper if needed.
I still can´t give you exact values, for bases with <250 remain k´s 25G should be okay. >250 and <500 k´s I think 50G should work.

[QUOTE=MisterBitcoin;478805]There is also no experience with so much k´s for yoyo with sr2sieve. I want to be 100% sure that this implementation works without any problems.[/QUOTE]
Just an observation (I don't really know what you are doing here, so if I say some stupid or unrelated stuff, forgive me).
In my experience (i.e. R66), sr2sieve is getting much slower when you deal with lots of k's, because the time to compute the tables is then comparable with the time to sieve. You should keep the number of k's in a chunk low enough to have the time for computing those tables not larger than 3-5% of the total sieving time (iirc).

Misterbitcoin, LaurV has a good point. For R411 on my machine, it took about 15-20 minutes to create the Legendre tables when using sr2sieve for the ~180 k's. You can save off one of the tables (with your first run of sr2sieve) with the -c switch but that only helps if you decide to run it a second time. You can then use the -C (upper case) switch to almost immediately load the tables upon a second run. But this only helps if someone at Yoyo is running it a second time or on more than one core.

The time taken to create the tables can vary widely. It's mostly instantaneous if there are fewer than 10 k's remaining. For R66 they would be so large that it would be impractical to use them. In that case sr2sieve with the -x switch is the way to go. It prevents the creation of the tables. It's much slower sieving than if the tables are created but is still much faster than srsieve.

The tables can be huge! Their size can vary widely even for the same number of k's. It seems to be base-specific. I had a base recently that had ~900 k's remaining at n=2500. I went to run sr2sieve on it for n=2500-10K and found that the tables took 1-2 hours to create and their size was ~3.5 GB! This did not work on that particular machine with only 4 GB of memory. So I ended up using sr2sieve with the -x switch. As a comparison R411 with ~180 k's remaining had a Legendre tables size of ~300-400 MB.

It's just something to keep in mind. The Yoyo folks might become annoyed if they have to wait too long for their sieve to start. They might not mind 15-20 minutes but if it takes an hour or more and it sucks up most of their memory on a machine that might not be good.

Good point!
I use -x an every base with more than 100 k´s remain, because it´s taking some time to build them.
I almost forgot to tell yoyo about that specific detail on sr2sieve!
I´ll let him know that he should add the -x switch to .abcd files containing more than 25 k´s. That should be an fair value, I guess. :smile:

I know that point, LaurV. I mean I "produced" the sieve files for Base S66. :max:
I´ll find a way to sieve such big bases soon. :) It will be an very short sieving range, which also means lots of lots WU´s.
Looking forward.
Greetings from my Workplace, LOL.

[QUOTE=MisterBitcoin;478874]
I almost forgot to tell yoyo about that specific detail on sr2sieve!
I´ll let him know that he should add the -x switch to .abcd files containing more than 25 k´s. That should be an fair value, I guess. :smile:[/QUOTE]

You could tell more than 100 k's. It rarely takes more than ~5 minutes for under 100 k's. But if you think any delay would concern them then maybe 25 k's is better.

How big is this file uncompressed and compressed if I create it with -c for e.g. 100k's or 500k's and so on?

[QUOTE=yoyo;478896]How big is this file uncompressed and compressed if I create it with -c for e.g. 100k's or 500k's and so on?[/QUOTE]

If you are talking about the Legendre tables, it varies widely by base and the size of the k's (not always necessarily the number of k's). For ~900 k's for base R381, it was 3.5 GB uncompressed and took 1-2 hours to create! For R411 with ~185 k's, which is the one that MisterBitcoin is working on for you, it was 300-400 MB uncompressed and took about 15 mins. to create, which I think would be manageable for you. I had another base recently with ~270 k's remaining and it only took 5-10 mins. and the table size was < 100 MB. Compressed all files would be about 1/5th to 1/7th that size.

But that was my experience. My machines are slow and only have ~4 GB of memory. Your experience may be faster but I think the table size should be about the same on all machines. It can vary a little by O.S. for the same k's and base.

You can see that there is no set rule on how big they can be based on number of k's. There is only general estimates. Here is what I would suggest: When MisterBitcoin gives you the file for R411, at the command prompt run sr2sieve with the -c switch one time yourself with the following command:
sr2sieve -P ??e9 -c -zz -i sieve-R411-25K-100K.txt

??= just some nominal amount larger than current sieve depth

You will see the Legender tables being created. The -c switch will create a file called sr2cache.bin. Observe the screen as it scrolls through the k's while the tables are being created but do not stop it until it is done with the tables. The sr2cache.bin file will not be created until the tables are done just as the sieving actually begins. At that point you can stop the sieve and see how big the file is. If it's not too big you can zip it and attach it for others to use.

If others use a previously created file they can use the -C (must be upper case) switch and specify the file name of the tables:
sr2sieve -P ??e9 -C sr2cache.bin -zz -i sieve-R411-25K-100K.txt

Doing it this way the sieve will begin almost immediately like you were sieving only 5-10 k's.

Alternative #1 if all of this sounds a little too complicated you can simply use the -x switch, which will not create the tables:
sr2sieve -P ??e9 -x -zz -i sieve-R411-25K-100K.txt

If the -x switch is used the sieve will be a fair amount slower.

Alternative #2: Just have everyone create their own tables if they don't mind waiting for a few minutes before the actual sieving begins.

Here is the benefit to Yoyo with sieving these files with a large number of k's: Because there will be a lot of factors found very quickly the work units can potentially be smaller compared to sieving fewer k's...and that's because our optimum final sieve depth is smaller due to our sieve n-range being smaller; 25K-100K vs. 200K-500K. The drawback is potentially having to mess with these tables. But if you're willing to wait for them to be created the # of factors found very quickly can be very large and so the work units could potentially be smaller.

Perhaps what we can do is let you know ahead of time about how big the file of the tables will be. We cannot specifically send you the file because the file is different for different O.S.'s. I found this out when I tried to use one on a Windows machine that was created by a Linux machine. But...maybe the tables are the same for all Windows machines. So it might not be bad.

Thanks, you answered my question already if the sr2cache.bin is portable between Windows/Linux/ARM.

I suggest I´ll sieve R411 on one of my servers.
For now I wanted to take care on bases with less than 15 k´s remain. Even that will be an massive amount of CPU-years.
I still have some resources to finish this, it will take some weeks until I got an nice sieve depth.

[QUOTE=MisterBitcoin;478928]I suggest I´ll sieve R411 on one of my servers.
For now I wanted to take care on bases with less than 15 k´s remain. Even that will be an massive amount of CPU-years.
I still have some resources to finish this, it will take some weeks until I got an nice sieve depth.[/QUOTE]

If it just you sieving, don't sieve R411 deeply. BOINC can test it a lot faster than you can sieve it and doesn't care much if it's undersieved. Just sieve it to P=1T or something like that. I've seen them test n=25K-100K ranges that have only been sieved to P=100G.

That said, if we can easily sieve deeply with Yoyo then we should. But if it's a big hassle or requires a lot of one person's resources then we should not.

For R411 if you don't think Yoyo would care to work on the file, I feel like P=1T is reasonable.

when someone could build me a batch file and an understandable instruction, i could sieve sth for you

Reserving R675 and R431 for sieving n=25K-100K.

Reserving R495 for sieving n=25K-100K.

R675 sieving is complete for n=25K-100K.

Admin edit: Moved from another thread. This is reference base S606 testing reservation:

sieve file done in 3-4 days. Hope you still wait for it, as its reserved.

[QUOTE=MisterBitcoin;480001]sieve file done in 3-4 days. Hope you still wait for it, as its reserved.[/QUOTE]

Ah damn. I forgot about that multiple base reservation that you had for sieving n=10K-25K bases that have < 1000 k's remaining. I'm currently in the middle of sieving it. I'll go ahead and stop.

How deep have you sieved? Can you just send the file to me on Friday? My machines will need work by then. If you've sieved to P>=200G that is enough for me.

[QUOTE=gd_barnes;480002]Ah damn. I forgot about that multiple base reservation that you had for sieving n=10K-25K bases that have < 1000 k's remaining. I'm currently in the middle of sieving it. I'll go ahead and stop.

How deep have you sieved? Can you just send the file to me on Friday? My machines will need work by then. If you've sieved to P>=200G that is enough for me.[/QUOTE]

I´m only sieving to P=75e9, which fits perfect for n=10-15K. (Notice: I sieve the whole range from 10K-25K to 75e9, after reaching N=15K I extend the sieve file to 150e9.)
For larger n-values I sieve deeper, but before remove the primed k´s. There is some "little" speed-boost, depending on the number of primed k´s.
If you already sieved higher feel free to go forward, I´ll stop it then. I should be at ~24G now. I haven´t checked awhile and noticed that I had an typo in my batch file. :no:

[QUOTE=MisterBitcoin;480023]I´m only sieving to P=75e9, which fits perfect for n=10-15K. (Notice: I sieve the whole range from 10K-25K to 75e9, after reaching N=15K I extend the sieve file to 150e9.)
For larger n-values I sieve deeper, but before remove the primed k´s. There is some "little" speed-boost, depending on the number of primed k´s.
If you already sieved higher feel free to go forward, I´ll stop it then. I should be at ~24G now. I haven´t checked awhile and noticed that I had an typo in my batch file. :no:[/QUOTE]

OK I will resume it. I had stopped it at P=~35G. For me optimum depth for the entire range is P=~200G. I can do that in a couple of days on my new I7. :-)

Sorry I forgot about your reservation.

On another topic, what is your status on R411 for n=25K-100K? That is a higher priority one for BOINC now. For all these n=25K-100K bases for BOINC, I'm just sieving them all to P=1T. That is plenty for them.

[QUOTE=gd_barnes;480044]OK I will resume it. I had stopped it at P=~35G. For me optimum depth for the entire range is P=~200G. I can do that in a couple of days on my new I7. :-)

Sorry I forgot about your reservation.

On another topic, what is your status on R411 for n=25K-100K? That is a higher priority one for BOINC now. For all these n=25K-100K bases for BOINC, I'm just sieving them all to P=1T. That is plenty for them.[/QUOTE]

All to 1T, thats gonna take some time. Indeed.
I´m sieving R411 to pmax=3T; ETA is now 4.03.2018.

[QUOTE=MisterBitcoin;480048]All to 1T, thats gonna take some time. Indeed.
I´m sieving R411 to pmax=3T; ETA is now 4.03.2018.[/QUOTE]

Is that March 4th? :-)

[QUOTE=gd_barnes;480050]Is that March 4th? :-)[/QUOTE]

Yes. 4th March. :smile:

R495 sieving is complete for n=25K-100K. Reserving S465 for sieving n=25K-100K.

MrBitcoin

On your YoYo graph showing sieve progress you have S218 being sieved to 750e15

That will take forever. I think you meant 750e12 for something sitting at 500K

Fixed, thanks.
Must have been a Typo done by me.

R213, n=500K-1M, p=750e12
R214, n=1M-5M, p=2e15

R431 sieving is complete for n=25K-100K.

S465 sieving is complete for n=25K-100K.

Reserving S810 for sieving n=50K-100K.

[QUOTE=MisterBitcoin;478874]Good point!
I use -x an every base with more than 100 k´s remain, because it´s taking some time to build them.[/QUOTE]

This is a mistake as long as you have reasonable memory. You can build a Legendre table on any base and you should at least try it out before deciding not to do it. I've done it with up to 1000 k's remaining. Even if it takes 30 minutes to an hour, sr2sieve is so much faster than srsieve or sr2sieve with the -x switch. My general rule is that the table has to take less than 2 hours to build and be < 3 GB in size. A month or so ago I did one with over 600 k's remaining. The file took an hour to build and was about 2 GB in size but in the long run it saved a tremendous amount of sieving time. Running it on a machine with 8 GB of RAM I was able to run 3 instances of it.

On all of the n=25K-100K sieve files that you have seen me do recently, all with 180-350 k's remaining, I have used sr2sieve after creating the Legendre table. The largest table was ~1.5 GB but most of them were 50-500 MB. Doing that I can easily sieve to P=1T on a nearly 10 year old quad in ~5-6 days.

[QUOTE=MisterBitcoin;476718]@Gary
Can you zip the remain k´s for all bases tested up to n=10K with less than 1,000 k´s?
Those bases should be R606, R877, R996, S606, S807 and S1005.
I´ll sieve them up to n=25K.

I´m also working on the sieve files done my yoyo@home, maybe I´ll upload them in the middle of the night or tomorrow.[/QUOTE]

How much longer for the sieve file on these bases? It's been almost 2 months. I've already tested S606 to n=25K and will soon be ready to test R606 for n=10K-25K.

What sieve depth are you at for R606? If you have passed P=250G that should be enough and you can post the file here.

See the last post for why using the -x switch is likely a mistake on many of these bases and is slowing you way down.

[QUOTE=gd_barnes;481288]How much longer for the sieve file on these bases? It's been almost 2 months. I've already tested S606 to n=25K and will soon be ready to test R606 for n=10K-25K.

What sieve depth are you at for R606? If you have passed P=250G that should be enough and you can post the file here.

See the last post for why using the -x switch is likely a mistake on many of these bases and is slowing you way down.[/QUOTE]

I was focusing on R411, which is now free to go.
Factors up to 2.43T attached.
I´m now going to R606, just give me a couple of days.

[QUOTE=MisterBitcoin;481318]I was focusing on R411, which is now free to go.
Factors up to 2.43T attached.
I´m now going to R606, just give me a couple of days.[/QUOTE]

Great thanks. My machines will need work in ~3-4 days so the timing will work out well.

S810 sieving is complete for n=50K-100K.

Reserving S576 for sieving n=25K-100K.

S576 has 219 k's remaining but 34 of those k's are effectively being searched by S24 and are already at n>100K. So I will be sieving the other 185 k's.

Reserving S646 for sieving n=25K-100K.

S576 sieving is complete for n=25K-100K. This includes the 185 k's not searched by base 24.

Reserving R936 and S936 for sieving n=25K-100K.

Ian is still working on S936 to n=25K and will be done in ~7-10 days. At that point I will begin sieving both bases together.

Pepi has sent me 8 files sieved by Yoyo. Information as follows:

Riesel bases: 281, 338, 370, 380, 410, 447, 452, and 516
All 2, 3, and 4 k's remaining.
n=100K-300K
P=50T

They are now posted on the reservations page.

:smile:

[QUOTE=gd_barnes;481746]Pepi has sent me 8 files sieved by Yoyo. Information as follows:

Riesel bases: 281, 338, 370, 380, 410, 447, 452, and 516
All 2, 3, and 4 k's remaining.
n=100K-300K
P=50T

They are now posted on the reservations page.

:smile:[/QUOTE]

And I will send rest ( four of them) they are finished today, all WU is returned.
So expect new mail tomorrow :)

[QUOTE=pepi37;481805]And I will send rest ( four of them) they are finished today, all WU is returned.
So expect new mail tomorrow :)[/QUOTE]

...and we now have sieve files posted for Riesel bases 526, 530, 532, and 579 for n=100K-300K. :-)

S646 sieving is complete for n=25K-100K.

Reserving S918 for sieving n=25K-100K.

S918 sieving is complete for n=25K-100K.

Some finished sieve files from yoyo. The next part will be send soon.

R22, n=2-5M; p=5e15
R27, n=3-5M, p=5e15
R94, n=1-5M, p=2e15
R221, n=400K-1M, p=750e12
R233, n=400K-1M, p=750e12

R936 and S936 sieving is complete for n=25K-100K.

Reserving R708 for sieving n=50K-100K.

R708 sieving is complete for n=50K-100K.

Reserving S606 for sieving n=25K-100K.

S606 sieving is complete for n=25K-100K.

Reserving S477 for sieving n=25K-100K.

R590 3 100K-300K *
R601 3 100K-300K *
R634 2 100K-300K *
R686 3 100K-300K *
R712 3 100K-300K *
R720 3 100K-300K *
R780 3 100K-300K *
R813 3 100K-300K *
R814 3 100K-300K *
R816 3 100K-300K *
R987 3 100K-300K *
S433 3 100K-300K *
S468 3 100K-300K *
S470 2 100K-300K *
S573 3 100K-300K *
S634 3 100K-300K *
S686 2 100K-300K *
S703 3 100K-300K *
S716 3 100K-300K *
S730 3 100K-300K *
S754 3 100K-300K *
S788 3 100K-300K *
S790 3 100K-300K *
S805 2 100K-300K *
S825 3 100K-300K *
S835 2 100K-300K *
S859 2 100K-300K *

Sieve depth as recommended 25e12
Sieve files created and sent to Yoyo.

S477 sieving is complete for n=25K-100K.

Reserving S711 for sieving n=25K-100K.

S711 sieving is complete for n=25K-100K.

Reserving R381 for sieving n=25K-100K.

R381 sieving is complete for n=25K-100K.

Reserving R598 for sieving n=25K-100K.

New set of sieve files for YOYO
 

R334 200K-1M
R354 200K-1M
R469 200K-1M
R496 200K-1M
R504 200K-1M
R505 200K-1M

sieve depth 50e13