sievepercentage=1
sievesize=1000000
with sievepercentage=1, I got biggest PPS and more chainspermin. Is it good?
Good question.. can anyone attest to this?
Increased PPS 1K-2K. Did not increase CPM for me (i7 860 @ 3.22 quad). 0 blocks 12 hrs.
Edit : Tried on testnet, it was the worst results I've seen yet. 1 block in 5 min, gave up.
Other notes (updating) ...
sieve% above 15 crashes client on testnet as soon as mining starts.
SS : 4000000 S% : 15% = 3 BPM
SS : 4000000 S% : 14% = 40 CPM, 6600 PPS, 3+ BPM
<-- sweet spot so far. Ended up beating best HP5 setting by a little after 10 min.
Does not work on mainnet for me.SS : 4000000 S% : 13% = 2.3 BPM
SS : 4000000 S% : 11% = 37 CPM, 6800 PPS, 2.6 BPM
SS : 2000000 S% : 14% = 36 CPM, 7284 PPS, 2.0 BPM
Works on mainnet @ 1849 PPS, 12 CPM (highest I've seen so far).
SS : 2200000 S% : 14% =
44 CPM, 7079 PPS, 2.1 BPM
Works on mainnet @ 1835, 10 CPM (highest so far)
Over a longer period of time the above settings may equal out. 15% gave block spurts of 4-6 @ a time, while 14% gave steady blocks over entire time and "appeared" faster due to this lack of stalls between blocks.
Update : Once again settings that work fine on testnet shut down the client immediately upon mining. It's the 4M setting which works fine for HP5. I'm going to try to find the max sievesize for my i7 again since it appears to be lower for HP6 than HP5 (is this due to the higher difficulty or difference in builds?). Update 2 : The highest sievesize I can get on mainnet (i7 quad) is 2200000.
Observation :
Higher sievesize settings always increased blocks per minute in HP5 & HP6. Adjusting sieve% also affected BPM's and it has sweet spots as you can see above. I recommend finding the highest sievesize first (that will work on mainnet for you), then adjust sieve% for best results (on testnet) to find your sweet spot. Anything above 2200000 would shut the client down immediately in HP6 (for my i7 quad).
Since it appears (to me at least) that a larger sievesize increases BPM's, I will mention that HP3 gave 2 BPM (in 10 min runs) on testnet with SS : 6553600 and this will work on mainnet. However, I'm not positive that large of a sievesize was even supported in HP3 and it may be going to a default setting. However, with that in mind I set the sievesize to the default and results were much worse.