[QUOTE=rogue;450412]What else is using CPU? Can you use -t 5 or -t 6?[/QUOTE]

Nothing else use cpu

1404 pepi 39 19 7500 244 0 S [COLOR=Red][B]74.9[/B][/COLOR] 0.0 274:36.01 sr2sieve
1402 pepi 39 19 7500 244 0 S [B][COLOR=Red]74.2[/COLOR][/B] 0.0 275:20.12 sr2sieve
1403 pepi 39 19 7500 244 0 S [COLOR=Red][B]72.2 [/B][/COLOR] 0.0 274:53.23 sr2sieve
1405 pepi 39 19 7500 244 0 S [COLOR=Red][B]71.9[/B][/COLOR] 0.0 275:19.42 sr2sieve
1401 pepi 39 19 10180 4888 1952 R [COLOR=Red][B]19.0[/B][/COLOR] 0.1 70:33.86 sr2sieve

This is screenshot from top using t-4 ( Yes, I sow 5 instances of sr2sieve)

Using -t 4 switch I got aprox 48Mp/s , but if I use four separate processes I got aprox 66Mp/s

And screenshot now show 100% CPU uttilization

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1637 pepi 39 19 10128 4616 1840 R [COLOR=Red][B]100.0[/B][/COLOR] 0.1 4:01.22 sr2sieve
1639 pepi 39 19 10236 4748 1936 R [COLOR=Red][B]100.0[/B][/COLOR] 0.1 3:56.49 sr2sieve
1643 pepi 39 19 10436 5084 1936 R [COLOR=Red][B]100.0[/B][/COLOR] 0.1 3:48.91 sr2sieve
1641 pepi 39 19 10340 4924 1880 R [COLOR=Red][B]98.8[/B][/COLOR] 0.1 3:52.62 sr2sieve

[QUOTE=MisterBitcoin;450407]S1027 is now at 4,3T.
I needed for this 1,5 months, on my biggest server...
I´d like to release it, it´s taking too long...[/QUOTE]

Can you Email me the file that you have? That is a good start for a huge effort.

[QUOTE=gd_barnes;450419]Can you Email me the file that you have? That is a good start for a huge effort.[/QUOTE]

Sended, factors removed. It´s now an .prp file. ;)

Status S86: 30,5T
Status S87: 15T

S86 sieved to p=50T.
File attached.

S564 and R564
 

S/R 564 is sieved to P=30e12 for all remaining k's from n=100k-500k.

Edit: Might help to actually attach the file.

I'll do S821 for n=200k-500k.

I found that many sieve file is well under-sieved: but also , maybe is problem in sieve depth ( in header) that is not correct, and sieve was made much deeper.
So when report sieve as done, maybe is good idea to update it to true sieve depth.

[QUOTE=pepi37;450777]I found that many sieve file is well under-sieved: but also , maybe is problem in sieve depth ( in header) that is not correct, and sieve was made much deeper.
So when report sieve as done, maybe is good idea to update it to true sieve depth.[/QUOTE]

To the best of my knowledge all of the sieve depths in the files are correct. I check that what people say they are sieved to is what is in the file. That said, if someone tells me the incorrect depth then it would be incorrect. I can't check everything.

Many files are well undersieved to P=100G. If someone wants to increase the sieve depth on those, that would be helpful.

[QUOTE=wombatman;450767]S/R 564 is sieved to P=30e12 for all remaining k's from n=100k-500k.

Edit: Might help to actually attach the file.[/QUOTE]

I'm out of town for 10 days and my old laptop won't handle 7zip files. Old Windows Vista just can't handle it so I have WinZip on it. Could you do an older zip of the files so that I can post them to the pages?

[QUOTE=gd_barnes;450789]To the best of my knowledge all of the sieve depths in the files are correct. I check that what people say they are sieved to is what is in the file. That said, if someone tells me the incorrect depth then it would be incorrect. I can't check everything.

Many files are well undersieved to P=100G. If someone wants to increase the sieve depth on those, that would be helpful.[/QUOTE]

Look at [B]wombatman[/B] post, and he says that he sieved at P=30e12 or 30000000000000 ( if I understand it)
But when you open 7Z file and look at header it says only 1000000000.
In future, with so many posts, it will be nearly impossible to find this particular post, when correct sieve depth is written. And if somebody continues, he will be lost some time until reach true depth for nothing

SR 564 is in zip file now :)

[QUOTE=pepi37;450794]Look at [B]wombatman[/B] post, and he says that he sieved at P=30e12 or 30000000000000 ( if I understand it)
But when you open 7Z file and look at header it says only 1000000000.
In future, with so many posts, it will be nearly impossible to find this particular post, when correct sieve depth is written. And if somebody continues, he will be lost some time until reach true depth for nothing

SR 564 is in zip file now :)[/QUOTE]

There is a bug in srfile/sr2sieve. The header won´t display the higher sieve depht.
I use 100e6 as initial sieve depht using srsieve. After sieving to (e.g.) 15e12 and deleting factors found using srfile the value keeps at 100e6. [I change that value manually using Notepad++]
This work fine if you use sr1sieve, but somehow only creates this bug for more k-values sieving.

[CODE]ABCD 29*564^$a+1 [100037] // Sieved to 1000000000 with srsieve[/CODE]
Only with srsieve as you can see. And why is it .abcd?