Re: [400GH/s] p2pool: Decentralized, DoS-resistant, Hop-Proof pool
This will "give" you 1 difficulty shares if i look correctly (i see alot of accepted on my gpu's but not so much on the miner node) and this will count your count of the shares from the miners node and give a payout to your adress (use adress as username, and no password) Then you still have some variance, but its less
.Can't I give p2pool an argument that forces specific difficulty shares?
And if setting lower difficulty gets more shares, why doesn't everyone just set theirs like that?
(perhaps lower difficult shares are worth less?)
Even if they are, at least i'd get some shares, instead of none.
In all the documentation I read, no miner documentation ever said that one should use servers with difficulty to a low number if you are hashing less than X....
I have read people suggest low hashers use server pools who serve lower difficulty.
Can't p2pool be configured to serve low difficulty? (i understand that the miners cannot choose difficulty tho)
You should probably concentrate on the Local Rate Graph on this page of your p2p node:
http://localhost:9332/static/graphs.html?Day
It uses the Difficulty 1 shares to judge how fast your miner is. You should use the setting that gives you the highest number of non-dead shares. As long as you are submitting lots of non-dead diff1 shares, the real shares will also come in time. Trying to experiment with the real diff700 shares is not very helpful because the variability is too great.
As a ballpark though you could expect 5% DOA with 1000ms, 10% with 2000ms etc. 5-10% orphans would also be normal on top of that depending on how well your p2pool node is connected and how smoothly your bitcoind is serving work.