[QUOTE=gd_barnes;469277]
Alternatively I suppose if it is a BOINC effort doing the sieving then the BOINC sieving folks wouldn't mind getting additional work-unit credits for sieving so, MisterBitcoin, perhaps we could attempt to sieve those to close to optimal depth.
[/QUOTE]

This is exactly what I had in mind- if BOINCers are doing both the sieving and the testing, then we should make decisions that minimize the total project length (sieve computations + LLR computations). This maximizes the productivity of BOINC, and finds primes sooner!

[QUOTE=VBCurtis;469295]This is exactly what I had in mind- if BOINCers are doing both the sieving and the testing, then we should make decisions that minimize the total project length (sieve computations + LLR computations). This maximizes the productivity of BOINC, and finds primes sooner![/QUOTE]

So, what do we have here.
The sieve depth:

For this test I´ve choosen 50e12 because we need two important things before sieving deeper:

-Validator
-post-processing to generate a file containing factors found

Yoyo is working on the validator, it might a few days until is working.

I asked pepi if he needs deeper sieve files for his searches, I´m offering the same to anyone working on a base too. The values will be around 1-5P (depends on N).

For BOINC-Bases I suggest to sieve them to a lower value then on user Bases. Something like that should be a good starting point:

10K-25K: 1e12
25K-100K: 15e12
100K-250K: 50e12
250K-500K: 150e12
500K-1M: 500e12
1M-3M: 2e15

I also want to focus on sieve files that are undersieved, see a few posts before.

Notice: For now 1 WU sieves a range of 50e9, if the project is out of beta we will sieve a range of 500e9. Yesterday we had 339 WUs running at the same time, just awesome!

For your calculations about sieve depth you must also consider base. It is not same sieve depth for base 9 and exponent 1M and base 1000 with exponent 1M :)

As soon you make validator is working OK I will sent you my sieve files for futher sieving and will join project with all my cores. Since you help me, I will help project :)

[QUOTE=MisterBitcoin;469302]Notice: For now 1 WU sieves a range of 50e9, if the project is out of beta we will sieve a range of 500e9. Yesterday we had 339 WUs running at the same time, just awesome![/QUOTE]

The time it takes to sieve 50e9 varies with sqrt(number of k values); a base with 300 k's remaining will take 10x as long as a base with 3 k's remaining. If it's OK for a WU length to vary by 10x, I suppose you don't have to care. But BOINC power allows you to sieve bases like R19 with ~1000 k's; you don't want to assign 100e9 per WU there!

The time also varies with sqrt(n-range); sieving 500k to 2M will be much slower than 25k-100k, even if the number of k's is the same. You'll struggle to make a one-size-fits-all approach for this project, if WU length matters.

S27
 

S27 has been sieved to P=250e12 for n=1.211-2M. I believe that was considered sufficient. There are 13,295 candidates remaining. File is attached!

We have done testing on R667.
R667 is sieved up to 20e12, factors are checked (all ok).
Booth sieve files attached.


I´ll take R93 to pmax=200e12.

[QUOTE=VBCurtis;469313]The time it takes to sieve 50e9 varies with sqrt(number of k values); a base with 300 k's remaining will take 10x as long as a base with 3 k's remaining. If it's OK for a WU length to vary by 10x, I suppose you don't have to care. But BOINC power allows you to sieve bases like R19 with ~1000 k's; you don't want to assign 100e9 per WU there!

The time also varies with sqrt(n-range); sieving 500k to 2M will be much slower than 25k-100k, even if the number of k's is the same. You'll struggle to make a one-size-fits-all approach for this project, if WU length matters.[/QUOTE]


I´m splitting each base into single sequences. That makes more WU´s, but it will reduce the size of upload and download files.


New record: 747 WU´s running overall, each contains a 500e9 range.

Taking S256 to pmax=150e12.

S320 reached p=100e12, file attached.


Notice: Factors checked with check-factors. No errors found.


Reserving R800 from n=500K-1M.

[QUOTE=MisterBitcoin;469451]Reserving R800 from n=500K-1M.[/QUOTE]

This base was already completed to n=1M. I've done it to n=800k and BOINC did the rest.

[QUOTE=unconnected;469456]This base was already completed to n=1M. I've done it to n=800k and BOINC did the rest.[/QUOTE]


It´s range n=1M-3M.

R93 reached P=200e12.
434 factors found, new sieve file attached.

S256 reached P=150e12
387 factors found, new sieve file attached.

Reserving the next bases:

[CODE]R103
R368
R1019
R1024
R1029[/CODE]

@Gary I didn´t reserved R102. :)