Author

Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 803. (Read 2591630 times)

legendary
Activity: 2324
Merit: 1125
Okay these are the result for running today for 11 hours at 251 Mhash

My miner reports: [251.34 Mhash/sec] [249 Accepted] [1 Rejected] [RPC (+LP)]

p2pool reports:

2012-02-02 18:55:01.238000 Pool: 157GH/s in 17350 shares (17354/17354 verified)
Recent: 0.13% >203MH/s Shares: 6 (0 orphan, 0 dead) Peers: 10 (0 incoming)
2012-02-02 18:55:01.238000 Average time between blocks: 0.41 days
2012-02-02 18:55:01.238000 Pool stales: 9% Own: 20±20% Own efficiency: 88±21%

This seems rather contradictionary to me:

Miner reports: 0.4%  stales (1 in 250)
p2pool reports 0% stales (0 in 6)
p2pool reports 20±20% (where does this number come from)

Also, why does it recognize only 6 of 249 submitted shares?

Can someone explain all this to me? Smiley
legendary
Activity: 960
Merit: 1028
Spurn wild goose chases. Seek that which endures.
Haven't received a payout for two days. Is this just another block drought or is something wrong with my setup?
I'm seeing 156GH/s so I'm not on the split chain.
legendary
Activity: 1378
Merit: 1003
nec sine labore
twmz,

there is one thing in my setup which is not "standard" and this is the fact that my miner runs from an usb key so I have the miner at home and p2pool and bitcoind at work, so there is some more latency, I suspect.

I don't have my numbers at hand, but I have a lot less shares (I have less MHs) and a lot more orphans and dead shares.

spiccioli.

Well, I've restarted p2pool this morning at 0900 GMT+1, tomorrow I'll let you know what numbers I see.

regards.

spiccioli
full member
Activity: 928
Merit: 101
Didn't do anything with a run_p2pool.py file or saw one at all for that matter.  Seems like it did autogenerate a pay address for me.

I pretty much followed Holliday's post on the first page of this thread to a tee except I'm not sure where he got the p2pool_0.8.1_c7feb00.zip file from (step 10).

And then I kind of veered off at step 13 because he uses cgminer in his guide instead of GUIMiner.

When I view that graphs page you linked it says "Install python-rrdtool!".

Will check tomorrow and try to figure it out then.  So tired and need sleep.
hero member
Activity: 742
Merit: 500
Read through this entire thread and didn't really any mention of setting up P2Pool with GUIMiner...

If I downloaded P2Pool from the original post, setup the bitcoin.conf file inside my appdata/bitcoin folder, am I pretty much good to go?

The username / pass match up with the ones I entered in the bitcon.conf:



Also had a receive address show up in my bitcoin wallet as "p2pool".  That was done automatically somewhere during this process?
What flags did you use on run_p2pool.py? If you didn't specify a pay address (with -a) then it makes one for you.

The username/password in your miner are NOT the used to access bitcoind.  The username can either be a payment address or any arbitrary name.  If you set the password to the password displayed during p2pool startup, you can track your miner on http://localhost:9332/graphs/
full member
Activity: 928
Merit: 101
Read through this entire thread and didn't really any mention of setting up P2Pool with GUIMiner...

If I downloaded P2Pool from the original post, setup the bitcoin.conf file inside my appdata/bitcoin folder, am I pretty much good to go?

The username / pass match up with the ones I entered in the bitcon.conf:



Also had a receive address show up in my bitcoin wallet as "p2pool".  That was done automatically somewhere during this process?
full member
Activity: 215
Merit: 100
It's at 156 GH/S. If it isn't around this, you might be on the split chain and should update your client (p2pool still works on the split chain, just more variance).

Thanks. After updating to a newer p2pool client, I am now seeing 156 GH/s.
legendary
Activity: 3878
Merit: 1193
Is it really possible that total p2pool size including both chains is 270 GH/s?
newbie
Activity: 23
Merit: 0
It's at 156 GH/S. If it isn't around this, you might be on the split chain and should update your client (p2pool still works on the split chain, just more variance).
full member
Activity: 215
Merit: 100
Has P2pool hash rate gone down? I am seeing ~115 GH/s.
hero member
Activity: 516
Merit: 643
I am running the latest stable version of BTCMiner (https://bitcointalksearch.org/topic/btcminer-open-source-bitcoin-miner-for-ztex-fpga-boards-215-mhs-on-lx150-40047) pointed at P2Pool.  After a few hours of running (I haven't been around when it fails) it throws an invalid length string exception and shuts down.  After this happens whenever I try to restart the miner it seems to be ineffective and constantly reports that it detects a new block via long polling.  To resolve it I have to kill and restart bitcoind, P2Pool, and BTCMiner.  Is there anyone experiencing a similar error in their miners and odd P2Pool behavior?

BTCMiner's exact exception would be helpful in determining the problem - can you pastebin it somewhere? I can't test it as I have no FPGA miner..
newbie
Activity: 20
Merit: 0
I am running the latest stable version of BTCMiner (https://bitcointalksearch.org/topic/btcminer-open-source-bitcoin-miner-for-ztex-fpga-boards-215-mhs-on-lx150-40047) pointed at P2Pool.  After a few hours of running (I haven't been around when it fails) it throws an invalid length string exception and shuts down.  After this happens whenever I try to restart the miner it seems to be ineffective and constantly reports that it detects a new block via long polling.  To resolve it I have to kill and restart bitcoind, P2Pool, and BTCMiner.  Is there anyone experiencing a similar error in their miners and odd P2Pool behavior?
legendary
Activity: 1378
Merit: 1003
nec sine labore
Ok I'll check next time I mine. The blue part is the part that is reporting me such awful numbers (16-23 % stales). Efficiency was 87% (plus/minus a number I don't recall)

The blue and the red parts are showing the same information in different ways:

Total submitted shares: 180 valid + 8 orphan + 5 dead = 193.
Stale % = (8 orphan + 5 dead) / 193 total = 0.067 = 6.7%

But it is the red part that tells you what kind of problem you have (orphan vs dead).

Of course, these numbers are only useful after p2pool has been running for a few days.  They start out at zero everytime you restart p2pool and for the first day or two, randomness will make it hard to know what the real pattern is.


twmz,

there is one thing in my setup which is not "standard" and this is the fact that my miner runs from an usb key so I have the miner at home and p2pool and bitcoind at work, so there is some more latency, I suspect.

I don't have my numbers at hand, but I have a lot less shares (I have less MHs) and a lot more orphans and dead shares.

spiccioli.

hero member
Activity: 737
Merit: 500
Ok I'll check next time I mine. The blue part is the part that is reporting me such awful numbers (16-23 % stales). Efficiency was 87% (plus/minus a number I don't recall)

The blue and the red parts are showing the same information in different ways:

Total submitted shares: 180 valid + 8 orphan + 5 dead = 193.
Stale % = (8 orphan + 5 dead) / 193 total = 0.067 = 6.7%

But it is the red part that tells you what kind of problem you have (orphan vs dead).

Of course, these numbers are only useful after p2pool has been running for a few days.  They start out at zero everytime you restart p2pool and for the first day or two, randomness will make it hard to know what the real pattern is.
legendary
Activity: 2324
Merit: 1125
Ok I'll check next time I mine. The blue part is the part that is reporting me such awful numbers (16-23 % stales). Efficiency was 87% (plus/minus a number I don't recall)
hero member
Activity: 737
Merit: 500
I meant to type Mhash  of course as I mentioned it's a HD6850

I have no idea what kind of stales they are, the p2pool application does not report anything that seems relevant. Also the amounts of rejects is see reported by my miner are vastly lower than these very high stale percentages.

Look for these line in the p2pool output:

2012-02-01 13:25:32.973102 Pool: 147GH/s in 17310 shares (17314/17314 verified) Recent: 1.39% >2045MH/s Shares: 180 (8 orphan, 5 dead) Peers: 39 (29 incoming)
2012-02-01 13:25:32.973229 Pool stales: 8% Own: ~7% (4-12%) Own efficiency: ~101% (95-103%)

The red part tells you how many and what kind of stales you are getting.  The blue part tells you how that compares to the pool as a whole.

newbie
Activity: 28
Merit: 0
I meant to type Mhash  of course as I mentioned it's a HD6850

I have no idea what kind of stales they are, the p2pool application does not report anything that seems relevant. Also the amounts of rejects is see reported by my miner are vastly lower than these very high stale percentages.
yes it does:
Quote
Recent: 0.14% >210MH/s Shares: 26 (2 orphan, 0 dead) Peers: 11 (1 incoming)
legendary
Activity: 2324
Merit: 1125
I meant to type Mhash  of course as I mentioned it's a HD6850

I have no idea what kind of stales they are, the p2pool application does not report anything that seems relevant. Also the amounts of rejects is see reported by my miner are vastly lower than these very high stale percentages.
newbie
Activity: 28
Merit: 0
I have consistently higher stales than the pool. Today I mined my HD8650 for 8 hours non-overclocked (so at ~210Mhz instead of ~250Mhz) and that did not improve it any. On average p2pool reports ~16%+-16 while the pool is usually about 8% (today it even reported 23%+-23% !)

Is there anything I can do about this?
mining on a CPU?
210/250Mhz doesnt make sense.
CPUs run at ~2Ghz, GPUs at ~1Ghz

are the stales dead or orphans? (dead = miner problem, orphan = network problem)
legendary
Activity: 2324
Merit: 1125
I have consistently higher stales than the pool. Today I mined my HD8650 for 8 hours non-overclocked (so at ~210Mhz instead of ~250Mhz) and that did not improve it any. On average p2pool reports ~16%+-16 while the pool is usually about 8% (today it even reported 23%+-23% !)

Is there anything I can do about this?
Jump to: