[1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool

[lueo]

The whole graph could be shown here, the current payout is dramatically down.

What do the other graphs look like?  Or instead of the graph, the output P2Pool is showing you.  Not enough information here to go on.

[Smoovious]

On the Current Payout graph, would it be possible to show when a coin was found and we collected the amount on the graph? A dot, or an asterisk or something...

Also, would it be possible to overlay another line, showing how many shares we currently have contributing to our payout share?

The program shows how many shares, stale, and dead, I have had in the current run, but having the currently contributing count available would be useful. I'm thinking of manually setting my difficulty higher, but wanna try and make sure I can keep from having 0-contributing-share periods.

-- Smoov

[Prattler]

http://blockchain.info/block-index/198300/00000000000007fe6fe7c139c4aa351efb4116e836169bb38f3fea7eaf270cc7

Lame.

GOT BLOCK FROM PEER! Passing to bitcoind! 5f1b56ad bitcoin: http://blockexplorer.com/block/00000000000007fe6fe7c139c4aa351efb4116e836169bb38f3fea7eaf270cc7

I got identified as the owner of this block, even though I was only relaying it Wonderful to see that p2pool blocks get distributed through 2 networks simultaneously, which should be a huge advantage, even if it was not enough this time.

[Ente]

Why my payout drop down so dramatically?

The timeframe is just one day here? With a handful blocks solved by p2pool a day you cant make emaningful conclusions. Sorry, but again it boils down to variance.. ;-)

Ente

[twmz]

Why my payout drop down so dramatically?

The timeframe is just one day here? With a handful blocks solved by p2pool a day you cant make emaningful conclusions. Sorry, but again it boils down to variance.. ;-)

Ente

He has 3.5 GH/s and shouldn't really see a lot of share-based variance.  His current payout isn't affected by the number of blocks found per day, and it changing that dramatically has to be an indication that something is wrong.  

The only thing that you haven't shared/shown is share orphan/dead rate.  Is that high?  What is shown in the p2pool console window for this line:

Code:

Shares: 203 (6 orphan, 3 dead) Stale rate: ~4.4% (2-9%) 

[Ente]

Ah, right, I didnt pay close enough attention to both of the axis ;-)

Ente

[lueo]

Yes, my hash rate is about 3.5GH/s.

My statistics is shown below:

2012-03-25 19:22:09.139878  Local: 3651MH/s in last 10.0 minutes Local dead on arrival: ~3.5% (2-6%) Expected time to share: 13.2 minutes
2012-03-25 19:22:09.139963  Shares: 303 (28 orphan, 4 dead) Stale rate: ~10.6% (7-15%) Efficiency: ~97.8% (93-102%) Current payout: 0.0371 BTC
2012-03-25 19:22:09.140187  Pool: 333GH/s Stale rate: 8.5% Expected time to block: 5.4 hours

Should I restart my p2pool? my version is 0.10.3

Why my payout drop down so dramatically?

The timeframe is just one day here? With a handful blocks solved by p2pool a day you cant make emaningful conclusions. Sorry, but again it boils down to variance.. ;-)

Ente

He has 3.5 GH/s and shouldn't really see a lot of share-based variance.  His current payout isn't affected by the number of blocks found per day, and it changing that dramatically has to be an indication that something is wrong.  

The only thing that you haven't shared/shown is share orphan/dead rate.  Is that high?  What is shown in the p2pool console window for this line:

Code:

Shares: 203 (6 orphan, 3 dead) Stale rate: ~4.4% (2-9%) 

[Icoin]

had a similar issue, after updating and restarting everything works well again.

Should I restart my p2pool? my version is 0.10.3

[lueo]

Update to the latest version (git pull), restarted it...

Still the same!

I have set an option "--fee 5.0", will it affect my current payout?

2012-03-25 21:12:28.718609  Local: 3538MH/s in last 10.0 minutes Local dead on arrival: ~1.4% (0-3%) Expected time to share: 14.6 minutes
2012-03-25 21:12:28.718762  Shares: 6 (0 orphan, 0 dead) Stale rate: ~0.0% (0-35%) Efficiency: ~108.1% (70-109%) Current payout: 0.0453 BTC
2012-03-25 21:12:28.718837  Pool: 347GH/s Stale rate: 7.5% Expected time to block: 5.1 hours

had a similar issue, after updating and restarting everything works well again.

Should I restart my p2pool? my version is 0.10.3

[Ente]

huh, tricky one!
It all looks good to me, on your end.
Could you paste a whole "block" of info from p2pool? Including sharechain-size, network-hashrate etc? Maybe some split-chain issue, or general share-chain issue? Either that (network probs outside your farm), or some of the graphs do lie..

Ente

[echris1]

Update to the latest version (git pull), restarted it...

Still the same!

I have set an option "--fee 5.0", will it affect my current payout?

[/quote]

Well, your payout has gone up again, but it will take a day or so of constant running to push that payout rate back up.

The fee shouldn't affect you, since the --fee tag is only applied to people mining on your node with their payout address as a username, for example if your running a public node. And even if you did do it that way, those fees should be put into the wallet on your P2Pool node. 

[lueo]

I have 2 questions:

1. Why did it go down?
2. Will it go up? Why?

It doesn't go up like echris1 said. It had going down from 0.5 to 0.03 and now it's 0.04. Way below the average.

Update to the latest version (git pull), restarted it...

Still the same!

I have set an option "--fee 5.0", will it affect my current payout?

Well, your payout has gone up again, but it will take a day or so of constant running to push that payout rate back up.

The fee shouldn't affect you, since the --fee tag is only applied to people mining on your node with their payout address as a username, for example if your running a public node. And even if you did do it that way, those fees should be put into the wallet on your P2Pool node. 
[/quote]

[cabin]

Update to the latest version (git pull), restarted it...

Still the same!

I have set an option "--fee 5.0", will it affect my current payout?

2012-03-25 21:12:28.718609  Local: 3538MH/s in last 10.0 minutes Local dead on arrival: ~1.4% (0-3%) Expected time to share: 14.6 minutes

The fee won't matter, but any miners using a real bitcoin address as the username won't show in your graph for current payouts. Check the address.. it probably has large balance by now.

[tynt]

I can't get 0.6rc4 to work anymore. bitcoin-qt is simply "Not responding" all the time. Is there a better version of bitcoin out there?

[forrestv]

I have 2 questions:

1. Why did it go down?
2. Will it go up? Why?

Are you mining to a different address by setting your miner's username to a Bitcoin address? The "current payout" graph only displays bitcoins going to the default address. Did you maybe change your miner's username to a Bitcoin address about 24 hours ago..?

[Ente]

I can't get 0.6rc4 to work anymore. bitcoin-qt is simply "Not responding" all the time. Is there a better version of bitcoin out there?

- use bitcoind instead bitcoin-qt
- is the bitcoin.conf right?
- is the blockchain completely loaded? (check with bitcoin-qt and/or "bitcoind --getinfo")
- you may use either the newest 0.6.x beta or the newest 0.5.y "stable beta"


sorry for the generic only answer ;-)

Ente

[Ente]

The "current payout" graph only displays bitcoins going to the default address.

Good to know! Does it "find" dynamic/changing default addresses? When you dont state an address via "-a" the address may change to a different local bitcoin wallet address.

Ente

[tynt]

- use bitcoind instead bitcoin-qt
- you may use either the newest 0.6.x beta or the newest 0.5.y "stable beta"

Using bitcoind now. Works fine. Looks like rc4 qt is broken, other ppl have same problems.
0.5 does not work, p2pool requires 0.6rc4+ (for BIP16 i guess).

[forrestv]

The bitcoin 0.5.4 backport works too - see the first post here for a link.

[lueo]

Thanks for forrestv's answering!

Yes, I've change my miners' username from "miner1" to "1NxxxxxxxxUYS" (a Bitcoin Address).

I really don't know that the "current payout" only display the payout of the default address. It's confusing, because I won't know the overall performance of my p2pool node.

Could p2pool seperate the graph to show the overall performance and individual miner's performance?

I have 2 questions:

1. Why did it go down?
2. Will it go up? Why?

Are you mining to a different address by setting your miner's username to a Bitcoin address? The "current payout" graph only displays bitcoins going to the default address. Did you maybe change your miner's username to a Bitcoin address about 24 hours ago..?