Author

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

member
Activity: 97
Merit: 10
Well when recoding p2pool, It would be Nice to solve the "payload too long" issue as well.

Does somebody know how to deal with this?  Huh  

Please check this post: https://bitcointalksearch.org/topic/m.10164796

 Roll Eyes

What is Your Bitcoind GetBlockTemplate Latency? Has You p2pool node external IP to see stats?


Thanks for the reply!

Well my stats looks like this:

Code:
P2Pool Status
Local rate 155.77 GH/s (DOA 3.67 GH/s / 2.35%) Shares Total: 2 (Orphan: 0, Dead: 1, Unknown: 1)
Global pool rate 1.93 PH/s (DOA 321.61 TH/s / 16.67%) Share difficulty 6,707,631.61
Current block value Expected time to share 2d 3h 22m 33 s
Total node payout if block found NOW Expected time to block 1d 3h 11m 10 s
Node peers [in] 2 / 30 [out] Node uptime 2d 6h 35m 22 s
Node p2pool version 13.5-73-g12ca9d8-dirty Protocol version 1300
Node efficiency 60.00% Node getwork latency 305 ms
Node fee 0% Node donation 0%

Bitcoin Status
Network rate 303.41 PH/s Blocks 339,372
Current block 998,775 bytes / 1,600 txs Block difficulty 43,971,662,056.08958
Hashes to win 9.22 EH Block probability per GH 5.295015761671106e-12%
Total Bitcoins Expected time to block 0h 0m 30 s
Exchange rate Block interval 0h 10m 30 s
Connections [in] 12 / 523 [out] Node uptime 2d 6h 37m 53 s
Node bitcoind version 99900 Protocol version 70002
Relay fee Peer latency 675 ms


I assume my Bitcoind GetBlockTemplate Latency is 675ms, right? From what I've read, the latencies are OK and they are stable when the "payload too long" error is not occurring. Only when the error comes up in the console of p2pool then those latencies are indeed skyrocketing. As I understand from the logs and statistics this payload error does not look like a cause from latencies, but latencies are the symptoms of the payload error. So where all the sudden arises this payload error from? Is it the "maxblocksize" of Bitcoind Core which is 1MB? Because the payload error is always in combination when the blocktime between blocks were +10mins (and +2000 transactions). Get the idea the problem comes from that direction.

Any thoughts?

legendary
Activity: 1258
Merit: 1027
legendary
Activity: 1500
Merit: 1002
Mine Mine Mine
may i humbly ask for a updated step by step noob proof guide on pypy ?

this should work for user using 64 bit linux: https://bitcointalksearch.org/topic/m.10135870

thx, i'll try to tinkle with it a bit while i polish up my linux skills
legendary
Activity: 1258
Merit: 1027
I suppose daemons has to be compiled with wallet enabled and run at the same machine as bitcoind and p2pool if succeed will create there mining address?

All on the same machine, yes - but p2pool won't create an address on other daemons, payments will go to the default daemon wallet address.

How many of those coins is there still a market for?

All except FSC & GRP... Wink

Pretty cool, nice way to add a little to the bottom line Smiley
hero member
Activity: 686
Merit: 500
WANTED: Active dev to fix & re-write p2pool in C
I suppose daemons has to be compiled with wallet enabled and run at the same machine as bitcoind and p2pool if succeed will create there mining address?

All on the same machine, yes - but p2pool won't create an address on other daemons, payments will go to the default daemon wallet address.

How many of those coins is there still a market for?

All except FSC & GRP... Wink
legendary
Activity: 1258
Merit: 1027
I suppose daemons has to be compiled with wallet enabled and run at the same machine as bitcoind and p2pool if succeed will create there mining address?

All on the same machine, yes - but p2pool won't create an address on other daemons, payments will go to the default daemon wallet address.

How many of those coins is there still a market for?
hero member
Activity: 686
Merit: 500
WANTED: Active dev to fix & re-write p2pool in C
I suppose daemons has to be compiled with wallet enabled and run at the same machine as bitcoind and p2pool if succeed will create there mining address?

All on the same machine, yes - but p2pool won't create an address on other daemons, payments will go to the default daemon wallet address.
full member
Activity: 238
Merit: 100
Sure: Bitcoin, Namecoin, I0coin, Devcoin, Huntercoin, Groupcoin & Fusioncoin. I was also mining ixcoin until it got all mined out  Sad
You're still mining all of those coins?  Wow... I stopped everything except for NMC.  Sure, I've got a boatload of some of those coins, but nowhere to do anything with them.  Like FSC... I've got a few million of the things, but the coin's completely dead in the water and no exchanges trade it.

Yeah, it does no harm to keep mining them in the slim hope someone might revive them....... Tongue

Nice. Can You share core versions You are using? I would like to try some but I do not want to make system unstable. Do You preffer any of them? I think they are all worthless but I can be wrong...

All daemons are the latest, cloned from git or downloaded binaries from their sites. I prefer Bitcoin of course, the rest are just a little bonus that I cash in every now & then - helps pay the bills  Wink

I suppose daemons has to be compiled with wallet enabled and run at the same machine as bitcoind and p2pool if succeed will create there mining address?
hero member
Activity: 686
Merit: 500
WANTED: Active dev to fix & re-write p2pool in C
Sure: Bitcoin, Namecoin, I0coin, Devcoin, Huntercoin, Groupcoin & Fusioncoin. I was also mining ixcoin until it got all mined out  Sad
You're still mining all of those coins?  Wow... I stopped everything except for NMC.  Sure, I've got a boatload of some of those coins, but nowhere to do anything with them.  Like FSC... I've got a few million of the things, but the coin's completely dead in the water and no exchanges trade it.

Yeah, it does no harm to keep mining them in the slim hope someone might revive them....... Tongue

Nice. Can You share core versions You are using? I would like to try some but I do not want to make system unstable. Do You preffer any of them? I think they are all worthless but I can be wrong...

All daemons are the latest, cloned from git or downloaded binaries from their sites. I prefer Bitcoin of course, the rest are just a little bonus that I cash in every now & then - helps pay the bills  Wink
full member
Activity: 238
Merit: 100
Sure: Bitcoin, Namecoin, I0coin, Devcoin, Huntercoin, Groupcoin & Fusioncoin. I was also mining ixcoin until it got all mined out  Sad

Nice. Can You share core versions You are using? I would like to try some but I do not want to make system unstable. Do You preffer any of them? I think they are all worthless but I can be wrong...
legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
Sure: Bitcoin, Namecoin, I0coin, Devcoin, Huntercoin, Groupcoin & Fusioncoin. I was also mining ixcoin until it got all mined out  Sad
You're still mining all of those coins?  Wow... I stopped everything except for NMC.  Sure, I've got a boatload of some of those coins, but nowhere to do anything with them.  Like FSC... I've got a few million of the things, but the coin's completely dead in the water and no exchanges trade it.
hero member
Activity: 686
Merit: 500
WANTED: Active dev to fix & re-write p2pool in C
Sure: Bitcoin, Namecoin, I0coin, Devcoin, Huntercoin, Groupcoin & Fusioncoin. I was also mining ixcoin until it got all mined out  Sad
full member
Activity: 238
Merit: 100
In all fairness, the huge memory use is not an issue for me and is a price worth paying for increased performance - which so far is the case. My DOA rate is lower so far, my latency is also lowering gradually & my recorded hash rate is slightly higher. So far so good.

It also shows how truly terrible & slow the standard python is for p2pool........

what version of bitcoin core are You running?

The latest: 0.9.4

My DOA rate has halved using pypy since I installed it - it was ~3-5%, but is now ~0.5-2.5% so I'm a happy hippy  Grin

Are you merge mining? My DOA sky rockets when merge mining. Plus, doesn't seem to be worth the effort as it's basically soloing, might as well gamble more and solo for BTC.

Yeah, merge mining 7 coins in total. Your BTC DOA rate shouldn't change when you're merge mining - sounds like it's not setup right.

7 coins? it interests me, can You tell me which coins?
sr. member
Activity: 248
Merit: 250
Are we there yet?
Super low share diff. Good time to get some shares NOW!
sr. member
Activity: 248
Merit: 250
Are we there yet?
Yeah, merge mining 7 coins in total. Your BTC DOA rate shouldn't change when you're merge mining - sounds like it's not setup right.

It's the damn S4. They really hate restarts.. and with merge mining, more restarts......

But thanks to CK's quick fix, works much better.
hero member
Activity: 686
Merit: 500
WANTED: Active dev to fix & re-write p2pool in C
In all fairness, the huge memory use is not an issue for me and is a price worth paying for increased performance - which so far is the case. My DOA rate is lower so far, my latency is also lowering gradually & my recorded hash rate is slightly higher. So far so good.

It also shows how truly terrible & slow the standard python is for p2pool........

what version of bitcoin core are You running?

The latest: 0.9.4

My DOA rate has halved using pypy since I installed it - it was ~3-5%, but is now ~0.5-2.5% so I'm a happy hippy  Grin

Are you merge mining? My DOA sky rockets when merge mining. Plus, doesn't seem to be worth the effort as it's basically soloing, might as well gamble more and solo for BTC.

Yeah, merge mining 7 coins in total. Your BTC DOA rate shouldn't change when you're merge mining - sounds like it's not setup right.
sr. member
Activity: 248
Merit: 250
Are we there yet?
In all fairness, the huge memory use is not an issue for me and is a price worth paying for increased performance - which so far is the case. My DOA rate is lower so far, my latency is also lowering gradually & my recorded hash rate is slightly higher. So far so good.

It also shows how truly terrible & slow the standard python is for p2pool........

what version of bitcoin core are You running?

The latest: 0.9.4

My DOA rate has halved using pypy since I installed it - it was ~3-5%, but is now ~0.5-2.5% so I'm a happy hippy  Grin

Are you merge mining? My DOA sky rockets when merge mining. Plus, doesn't seem to be worth the effort as it's basically soloing, might as well gamble more and solo for BTC.
hero member
Activity: 686
Merit: 500
WANTED: Active dev to fix & re-write p2pool in C
In all fairness, the huge memory use is not an issue for me and is a price worth paying for increased performance - which so far is the case. My DOA rate is lower so far, my latency is also lowering gradually & my recorded hash rate is slightly higher. So far so good.

It also shows how truly terrible & slow the standard python is for p2pool........

what version of bitcoin core are You running?

The latest: 0.9.4

My DOA rate has halved using pypy since I installed it - it was ~3-5%, but is now ~0.5-2.5% so I'm a happy hippy  Grin
full member
Activity: 238
Merit: 100
In all fairness, the huge memory use is not an issue for me and is a price worth paying for increased performance - which so far is the case. My DOA rate is lower so far, my latency is also lowering gradually & my recorded hash rate is slightly higher. So far so good.

It also shows how truly terrible & slow the standard python is for p2pool........

what version of bitcoin core are You running?
full member
Activity: 238
Merit: 100
may i humbly ask for a updated step by step noob proof guide on pypy ?

this should work for user using 64 bit linux: https://bitcointalksearch.org/topic/m.10135870
Jump to: