S406 sieved to p=50T.
Checked for alg. factors, nothing found.

These file was finished 04.02, failed to upload.

Reserving S55 (n=1-3M, all k´s) for sieving.
Estimated time needed: one month
Pmax: now running to 75T; maybe deeper depending on time per factor


The last Part from S66 is in work. maybe ~3 weeks.

S66 is done, files are en route via Mail.
Also reserving S81 for n=500K-1M, P=50e12

S55 sieve reached p=75T. File attached.

Reserving S236 for n=100K-250K with pmax=20T

[QUOTE=MisterBitcoin;454759]S66 is done, files are en route via Mail.
Also reserving S81 for n=500K-1M, P=50e12[/QUOTE]

Is the sieve depth for S66 P=100G ? You originally said that you would sieve it to P=500G and then said you would sieve it to P=100G. The depth is not specified here or in your Email. It is also not correct in the files that you sent me.

P=100G is not nearly a deep enough sieve for n=25K-100K for any base except maybe base 3. I suppose that BOINC doesn't care though.

[QUOTE=gd_barnes;454787]P=100G is not nearly a deep enough sieve for n=25K-100K for any base except maybe base 3. I suppose that BOINC doesn't care though.[/QUOTE]

For base 3, optimal sieve is (dependent on your computersystem) somewhere from 35G-50G ... on my system (both Haswell and Sandy Bridge) optimal sievedepth for n=25K-100K for R3 was 35G per 1G range :smile:

[QUOTE=gd_barnes;454787]Is the sieve depth for S66 P=100G ? You originally said that you would sieve it to P=500G and then said you would sieve it to P=100G. The depth is not specified here or in your Email. It is also not correct in the files that you sent me.

P=100G is not nearly a deep enough sieve for n=25K-100K for any base except maybe base 3. I suppose that BOINC doesn't care though.[/QUOTE]

I´m trying to combine these 4 files into 1 file and will sieve deeper, depending of time needed.

[QUOTE=MisterBitcoin;454804]I´m trying to combine these 4 files into 1 file and will sieve deeper, depending of time needed.[/QUOTE]

Too much k´s for sr2sieve. (all 12.000 k´s in one file)
I´m not going to work on S66 for now.

Gary, can you add the current user working on a base listed in the table (extra column)? There is an upcoming stress test on SRBase soon so I can pickup some more bases not reserved by anyone else yet.

[QUOTE=MisterBitcoin;454814]Too much k´s for sr2sieve. (all 12.000 k´s in one file)
I´m not going to work on S66 for now.[/QUOTE]

I'm confused- you reported S66 done, but rather than state the exact depth you searched you tell us you won't work on it. Huh?

As for sr2 not liking so many k's: you may wish to try the -x flag. sr2sieve runs more slowly under -x, but with a fair bit less memory; it's still roughly twice as fast as srsieve when run this way. I haven't tried 12000 k's, though!

[QUOTE=VBCurtis;454828]I'm confused- you reported S66 done, but rather than state the exact depth you searched you tell us you won't work on it. Huh?

As for sr2 not liking so many k's: you may wish to try the -x flag. sr2sieve runs more slowly under -x, but with a fair bit less memory; it's still roughly twice as fast as srsieve when run this way. I haven't tried 12000 k's, though![/QUOTE]

I splitted the base in 4 smaller parts, in the hope it will be faster (hehe, it isn´t).
I was just thinking that it will be faster to sieve p-Range: 100-250G with all 12000 k´s in 1 sieve file.
So: sr2sieve -i input.abcd -p 100e9 -P 250e9 -x -vv
And surprise: "sr2sieve stopped working" right after he tried to start sieving, so 12K might be too much k´s.
Any part should be at 100G.

PS: I use -x for sieves with >100 k´s, its skipping the lookup tables with is time consuming.
PSS: I´m on travel and wont have a good network connection, I´ll answer any questions on 17/03/2017.