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

I was just looking at the charts and was hit by several clumps of tumbleweed..........

OK, in the graphs I found - "getwork latency mean 0.787s".

Another thing that has me worried is the "Expected after mining for 24 hours" is only half of what I get on a PPS server.

This may be the cause of your DOA. It was already said here, but you shouldn't have that many connections on your bitcoind. The network code for bitcoin isn't yet optimized and with that many connections you're effectively harming yourself and the network as a whole...

Changing queue to zero cut my rejects down to about 6 percent. I have not tried changing the threads because that will halve my speed, right?

Where do I find GBT latency?

Try change to:
What is your GBT latency? 50% is soo high stale.

Thanks.

I'm trying to like p2pool, but I'm getting 50% rejects. I have a good cable internet connection with nothing else significant running on it.

Does it matter if I run bitcoin-qt vs. bitcoind?

Here's my cgminer config:

err, I killed it for now.  Have to redownload the blockchain, messed up while recompiling w/ higher fee settings.

I believe it was around 85 shares with 3 orphans.... with the 30 outgoing connections.   The precompiled version only allows you to set it to 10, however

ed: nm, found the stats file.  was 87 shares, 4 orphans and 3 DOA.... vs the 72 shares, 9 orphans, and 2 DOA earlier.  the DOA was probably just random chance.  don't think so for orphans

No.  Yes.

Is it necessary to use a bitcoin address on the command line that exists in the bitcoind instance you are running? For example, could you mine to a cloud based address (blockchain.info) that didn't exist on your local bitcoind?

I recompiled to do 30 outgoing connections and restarted, has been running about an hour or two so far...   nothing else has changed, didn't reload bitcoind or change anything else running on the server.  I guess I'll also mention that the pool DOA rate was ranging from 15-18% when I switched

Sample size isn't big enough now, but maybe in 5 or 6 hours

(you can see the swapover on my graph quite clearly @ the 9pm indicator)

sure, but they aren't being broadcast fast enough across the network.   there wouldn't be so many orphans, if there wasnt a problem

i just had another share orphaned, that actually had a child (bitcoin address was 1Cgxxxxxxxxx)...  5 seconds later, both mine and 1Cg's were gone and replaced with another tree.

that's happened once approx. 2 1/2 months for the bitcoin blockchain  (the 2nd instance being on 10-07).  

maybe change the difficulty to even out to three per minute instead of the current... five, I think it is?

I'm at 72 shares, 9 orphans, 2 DOA..   my p2pool server is located on a major hub @ hetzner, I also get 10ms ping times to the OVH french datacenter....  bandwidth limits are 1gbit/1gbit.    i have a bitcoind that has 800 connections which was the 'hub' node on blockchain ever since it was implemented until a few days ago (it keeps dropping me and I don't run it 24/7 anymore).... so, i think it pushes things out fairly quickly.

the attitude people have about orphans on the p2pool network is troublesome.  it's not something that should exist to the extent that it does

this dosnt matter, shares are being broadcasted.

illegal?  it's just some hetzner server i've had for like 9 months =p

well, the higher the hashrate the more shares that originate from there was my thinking.  i'll try the outgoing thing later... thanks

5.*.*.* is illegal.

if ur pool is accessable then just wait otherwise use --outgoing-conns
hashrate of the pool dosnt matter.

hmm, do you (or anyone else) have a list of all the p2pool nodes that are connectable (i guess there's an -addnode equivalent?) that sustain 3+ ghash??


oh, everyone feel free to addnode 5.9.24.81 in p2pool list

it may be slower, u wont get orphans due to that since u sibmit ur shares to the p2pool sharechain. i usually got 0 orphans and some doas due to the reason i got 100 connections to other nodes.

right, i knew about that, re: transaction fees.  the larger block size could result a few more ms (given that all of p2pool and bitcoind reside on a ramdisk), but some other person was reporting less than .10 seconds on the 'Bitcoind GetBlockTemplate Latency' stat.. (correct me if I'm wrong)

would it be faster if it only had 8 outgoing connections?  but, then, would I not also be causing more orphans by receiving blocks from the network slower?  i don't know how else to explain the above orphan.  i 'skipped ahead' to the next block, found a share, and then i 'skipped ahead to the next block' (same one) again, and it was counted as an orphan.

'Punishing share for 'Block-stale detected! 51d8cfe38e4d76c45a9bd23fcbed5c93f93dd77ded0526a434 < 4f7085c5ec1a3d8eb416418e54f800e938d43b55c169ea0c40f'! Jumping from b284721e to 18d04958!'

??

because the blocks in the p2pool sharechain or bitcoin sharechain became invalid/stale.

block value is always different due to the reason that all transaction fees are included in this number, the more transactions the higher a block value.

also, can someone clarify what this means:

2012-12-22 14:34:37.330552 Skipping from block 4f7085c5ec1a3d8eb416418e54f800e938d43b55c169ea0c40f to block 51d8cfe38e4d76c45a9bd23fcbed5c93f93dd77ded0526a434!
2012-12-22 14:34:38.159596 P2Pool: 17399 shares in chain (9699 verified/17403 total) Peers: 8 (2 incoming)
2012-12-22 14:34:38.159652  Local: 6892MH/s in last 10.0 minutes Local dead on arrival: ~4.1% (2-6%) Expected time to share: 6.8 minutes
2012-12-22 14:34:38.159672  Shares: 17 (0 orphan, 0 dead) Stale rate: ~0.0% (0-19%) Efficiency: ~117.5% (95-118%) Current payout: 0.0511 BTC
2012-12-22 14:34:38.159693  Pool: 323GH/s Stale rate: 14.9% Expected time to block: 12.4 hours
2012-12-22 14:34:38.692333 Punishing share for 'Block-stale detected! 51d8cfe38e4d76c45a9bd23fcbed5c93f93dd77ded0526a434 < 4f7085c5ec1a3d8eb416418e54f800e938d43b55c169ea0c40f'! Jumping from b284721e to 18d04958!
2012-12-22 14:34:39.114153 GOT SHARE!  ab9d1818 prev 18d04958 age 8.55s
2012-12-22 14:34:39.124374 New work for worker! Difficulty: 1.286614 Share difficulty: 652.069851 Total block value: 25.000000 BTC including 0 transactions
2012-12-22 14:34:39.132938 New work for worker! Difficulty: 1.286614 Share difficulty: 652.069851 Total block value: 25.000000 BTC including 0 transactions
2012-12-22 14:34:39.373962 New work for worker! Difficulty: 1.259615 Share difficulty: 652.069851 Total block value: 25.000000 BTC including 0 transactions
2012-12-22 14:34:41.161616 P2Pool: 17400 shares in chain (9701 verified/17405 total) Peers: 8 (2 incoming)
2012-12-22 14:34:41.161679  Local: 6910MH/s in last 10.0 minutes Local dead on arrival: ~4.1% (2-6%) Expected time to share: 6.7 minutes
2012-12-22 14:34:41.161698  Shares: 18 (0 orphan, 0 dead) Stale rate: ~0.0% (0-18%) Efficiency: ~117.2% (96-118%) Current payout: 0.0542 BTC
2012-12-22 14:34:41.161719  Pool: 324GH/s Stale rate: 14.7% Expected time to block: 12.4 hours
2012-12-22 14:34:44.164537 P2Pool: 17396 shares in chain (9700 verified/17400 total) Peers: 8 (2 incoming)
2012-12-22 14:34:44.164590  Local: 6915MH/s in last 10.0 minutes Local dead on arrival: ~4.0% (2-6%) Expected time to share: 6.7 minutes
2012-12-22 14:34:44.164608  Shares: 18 (0 orphan, 0 dead) Stale rate: ~0.0% (0-18%) Efficiency: ~117.2% (96-118%) Current payout: 0.0542 BTC
2012-12-22 14:34:44.164629  Pool: 324GH/s Stale rate: 14.7% Expected time to block: 12.4 hours
2012-12-22 14:34:47.166613 P2Pool: 17396 shares in chain (9700 verified/17400 total) Peers: 8 (2 incoming)
2012-12-22 14:34:47.166696  Local: 6922MH/s in last 10.0 minutes Local dead on arrival: ~4.0% (2-6%) Expected time to share: 6.7 minutes
2012-12-22 14:34:47.166730  Shares: 18 (0 orphan, 0 dead) Stale rate: ~0.0% (0-18%) Efficiency: ~117.2% (96-118%) Current payout: 0.0542 BTC
2012-12-22 14:34:47.166757  Pool: 324GH/s Stale rate: 14.7% Expected time to block: 12.4 hours
2012-12-22 14:34:50.169344 P2Pool: 17396 shares in chain (9700 verified/17400 total) Peers: 8 (2 incoming)
2012-12-22 14:34:50.169401  Local: 6942MH/s in last 10.0 minutes Local dead on arrival: ~4.0% (2-6%) Expected time to share: 6.7 minutes
2012-12-22 14:34:50.169420  Shares: 18 (0 orphan, 0 dead) Stale rate: ~0.0% (0-18%) Efficiency: ~117.2% (96-118%) Current payout: 0.0542 BTC
2012-12-22 14:34:50.169440  Pool: 324GH/s Stale rate: 14.7% Expected time to block: 12.4 hours
2012-12-22 14:34:50.405453 New work for worker! Difficulty: 1.410955 Share difficulty: 652.069851 Total block value: 25.000000 BTC including 0 transactions
2012-12-22 14:34:52.592338 Skipping from block 4f7085c5ec1a3d8eb416418e54f800e938d43b55c169ea0c40f to block 51d8cfe38e4d76c45a9bd23fcbed5c93f93dd77ded0526a434!
2012-12-22 14:34:53.172031 P2Pool: 17396 shares in chain (9700 verified/17400 total) Peers: 8 (2 incoming)
2012-12-22 14:34:53.172114  Local: 6972MH/s in last 10.0 minutes Local dead on arrival: ~4.0% (2-6%) Expected time to share: 6.7 minutes
2012-12-22 14:34:53.172139  Shares: 18 (0 orphan, 0 dead) Stale rate: ~0.0% (0-18%) Efficiency: ~117.2% (96-118%) Current payout: 0.0543 BTC
2012-12-22 14:34:53.172165  Pool: 324GH/s Stale rate: 14.7% Expected time to block: 12.4 hours
2012-12-22 14:34:53.965183 New work for worker! Difficulty: 1.572481 Share difficulty: 652.069851 Total block value: 25.000000 BTC including 0 transactions
2012-12-22 14:34:53.974331 New work for worker! Difficulty: 1.572481 Share difficulty: 652.069851 Total block value: 25.000000 BTC including 0 transactions
2012-12-22 14:34:54.237588 New work for worker! Difficulty: 1.581362 Share difficulty: 652.069851 Total block value: 25.283100 BTC including 376 transactions
2012-12-22 14:34:54.293442 New work for worker! Difficulty: 1.581362 Share difficulty: 652.069851 Total block value: 25.283100 BTC including 376 transactions
2012-12-22 14:34:54.497860 New work for worker! Difficulty: 1.581362 Share difficulty: 652.069851 Total block value: 25.283100 BTC including 376 transactions
2012-12-22 14:34:56.173854 P2Pool: 17396 shares in chain (9700 verified/17400 total) Peers: 8 (2 incoming)
2012-12-22 14:34:56.173919  Local: 6969MH/s in last 10.0 minutes Local dead on arrival: ~4.2% (2-7%) Expected time to share: 6.7 minutes
2012-12-22 14:34:56.173947  Shares: 18 (1 orphan, 0 dead) Stale rate: ~5.6% (0-26%) Efficiency: ~110.7% (87-117%) Current payout: 0.0507 BTC
2012-12-22 14:34:56.173969  Pool: 324GH/s Stale rate: 14.7% Expected time to block: 12.4 hours





it still seems to me that p2pool punishes good connections, by DOA'ing and orphaning valid shares, based on other ppls slow connections?    and why do i skip blocks like 4 or 5 times?

i've only been running it for an hour, but my "Bitcoind GetBlockTemplate Latency" is 0.15-0.20s..... is this the same thing?       don't see how it could be much faster, as it runs off a ram drive already

maybe having 800 outgoing connections in bitcoind slows it down?

i've noticed that i'm showing around 25.75 block value (with fees) while everyone else is 25.2 or less.   i guess that would slow it down?  

scratch.

example:

http://nogleg.com:9332/static/share.html#00000000003cc762db443f6f0a2df00b83e33f14a7fe021c22c740b23f8cd051

vs

http://nogleg.com:9332/static/share.html#00000000004057867aca8a5eeee954d4a512f572e2df86ae981092caff8f4f1d
http://nogleg.com:9332/static/share.html#00000000001700565889f549a456173c2595dc84fd98db13d3c9a8de9f9882c9
http://nogleg.com:9332/static/share.html#00000000002ee676f00cc3be921bc9cdffdaaa10a3558843e329e2555e24401f

(the next 3)