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

p3yot33at3r

sr. member

Activity: 266

Merit: 250

With all these S7's flying out the door, p2pool is missing out due to the usual bitmain firmware that broke cgminer.

I'd like to suggest starting a bounty for kano to do his magic on the S7 as he did with previous bitmain firmwares - I think it would encourage more miners to p2pool if they knew their S7's worked properly here.

We need moar powa!

Meuh6879

legendary

Activity: 1512

Merit: 1012

Quote from: sawa on November 22, 2015, 06:40:09 AM

Finds blocks very rarely. Why is that?

because global hashrate on P2Pool don't evolve ... but Bitcoin hashrate skyrocket Grin

Meuh6879

legendary

Activity: 1512

Merit: 1012

Quote from: TTravis on November 20, 2015, 08:42:56 AM

I am looking for suggestions as to parameters for bitcoin.conf, or anything else that will help me run better.

you can tweak on relay fee for example ... to catch free transaction and catch the longest chain.

Code:

minrelaytxfee=0.0000001
mintxfee=0

but be carefull, it's take more CPU and RAM to keep the mempool backlog.
use an bitcoin XT if you can not handle this job ... with this tweak :

Code:

maxmempooltx=50000

windpath

legendary

Activity: 1258

Merit: 1027

Yea they have a lot of inaccurate data, try sendrawtransaction from your server, then you will know it's relaying Wink

p3yot33at3r

sr. member

Activity: 266

Merit: 250

Blockchain.info is notorious for being inaccurate - as long as your wallet has connections, you are OK. It also helps to forward port 9333 to your host running p2pool, as well as running the relaynetworkclient: https://github.com/TheBlueMatt/RelayNode

sawa

legendary

Activity: 1308

Merit: 1011

Ok.
Another question:
Why stopped the transactions relayed through my node: https://blockchain.info/ip-address/82.200.205.30
Last transaction on 7/22/2015 6:16:05
I can not remember that there was - may be updated wallet or p2pool.
Port 8333 is open:

Quote

iptables -L INPUT -n -v
Chain INPUT (policy ACCEPT 981K packets, 285M bytes)
pkts bytes target prot opt in out source destination
29M 13G ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:8333
1 28 ACCEPT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:8333

I see a similar situation at many nodes:
http://elizium.name:9332/static/ https://blockchain.info/ip-address/95.170.95.133 - last transaction 2015-07-31 18:27:44
http://cammello.agaland.it:9332/static/ https://blockchain.info/ip-address/159.253.96.225 - last transaction 2015-07-31 19:08:04
http://61.219.120.109:9332/static/ https://blockchain.info/ip-address/61.219.120.109 - last transaction 2015-07-31 09:58:05
...etc, nodes through which the transaction never took place still more.

p3yot33at3r

sr. member

Activity: 266

Merit: 250

That stat is your share rate.

sawa

legendary

Activity: 1308

Merit: 1011

Quote from: jonnybravo0311 on November 22, 2015, 11:32:36 AM

What orphaned blocks? P2Pool hasn't orphaned a block in a very long time. Yes we are having a run of bad luck, but that's just what it is: bad luck. It happens.

I look at my stats http://crypto.office-on-the.net:9332/static/
What is it?:

Quote

Total: 305 (Orphan: 28, Dead: 25)

jonnybravo0311

legendary

Activity: 1344

Merit: 1024

Mine at Jonny's Pool

What orphaned blocks? P2Pool hasn't orphaned a block in a very long time. Yes we are having a run of bad luck, but that's just what it is: bad luck. It happens.

notbatman

legendary

Activity: 2212

Merit: 1038

I've also noticed more heat and less coins and wonder about the orphan block rate.

sawa

legendary

Activity: 1308

Merit: 1011

Finds blocks very rarely. Why is that?

Code:

Age Found Block # Block Hash Reward Miners Share Luck
6d 9h 1m 58s 2015-11-16 02:09:55 383770 00000000000000000055c0b4c9d8efb7ccc25a7425bab77c75bf91bca2a8477e 25.08297515 237 a2a8477e 147.14%
8d 7h 50m 34s 2015-11-14 03:21:19 383473 00000000000000000ee7628fbd822560b7bb206bfc4926090289c8c86992c12f 25.06613403 256 6992c12f 33.46%
15d 21h 12m 17s 2015-11-06 13:59:36 382316 000000000000000000d82908dea0384c57649f6ff5ff7faae93e53eaed06f597 25.00020420 265 ed06f597 89.21%

Until last month (for a year) mining on p2pool was the most profitable. Now I only heat the planet.
Should it be so?
Perhaps there is an error in the source code?
There are a lot of orphans and no blocks on all nodes.

p3yot33at3r

sr. member

Activity: 266

Merit: 250

No, it's just letting you know it's dropped a bad node - purely informational.

Mine on Wink

TTravis

full member

Activity: 165

Merit: 100

Is this something I should be concerned abut:

2015-11-20 13:34:34.084452 Peer sent entire transaction 7f603cd04bae7b638b6828c0b642c0d9328382367dfbcb34bb6dfb8ff42be7ff that was already received
2015-11-20 13:34:36.845494 > in handle_share_hashes:
2015-11-20 13:34:36.845633 > Traceback (most recent call last):
2015-11-20 13:34:36.845706 > Failure: twisted.internet.defer.TimeoutError: in GenericDeferrer
2015-11-20 13:34:36.846293 Lost peer 113.200.208.21:36448 - Connection was aborted locally, using.
2015-11-20 13:34:37.066870 P2Pool: 17342 shares in chain (17346 verified/17346 total) Peers: 9 (2 incoming)
2015-11-20 13:34:37.067000 Local: 67720GH/s in last 10.0 minutes Local dead on arrival: ~10.4% (8-13%) Expected time to share: 31.0 minutes

Thanks,

Tom

windpath

legendary

Activity: 1258

Merit: 1027

Quote from: TTravis on November 20, 2015, 10:19:29 AM

...
I'll do some research and find out what peers might be better. Where do you specify the list of peers?
...

Peers are added on the command line with the -n flag (note: if they use a custom port, include it ip_address:port).

Example:

Code:

./run_p2pool.py --address your_payout_address --outgoing-conns 10 -n 54.235.94.19 -n another_ip -n annother_ip rpc_user rpc_pass

Open source node scanner:
https://github.com/litecoin-project/p2pool-scanner

Online implementation of above:
http://p2pool.co/

p3yot33at3r

sr. member

Activity: 266

Merit: 250

Quote from: jonnybravo0311 on November 20, 2015, 10:26:04 AM

As far as I know, there is currently no custom firmware for the S7. The S5, however, does have updated firmware. It's based on cgminer 4.8.0. You can find it here: https://www.nicehash.com/sw/SD-S5-20150415_nicehash_perf_graphs.tar.gz. I'm not sure, but there might be another version for the S5 around somewhere... the one I linked above is from NiceHash and provides extranonce support along with some graphs.

If I remember correctly, that nicehash version does not submit stale shares.....

Yup, here it is:

https://bitcointalksearch.org/topic/m.12695616

Richy_T

legendary

Activity: 2576

Merit: 2267

1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k

This is the one I'm using for my S5. Seemed to show some improvement for me though that could be because the pool hash rate is dropping and I have a bigger share.

https://bitcointalksearch.org/topic/m.12983474

jonnybravo0311

legendary

Activity: 1344

Merit: 1024

Mine at Jonny's Pool

As far as I know, there is currently no custom firmware for the S7. The S5, however, does have updated firmware. It's based on cgminer 4.8.0. You can find it here: https://www.nicehash.com/sw/SD-S5-20150415_nicehash_perf_graphs.tar.gz. I'm not sure, but there might be another version for the S5 around somewhere... the one I linked above is from NiceHash and provides extranonce support along with some graphs.

TTravis

full member

Activity: 165

Merit: 100

Thanks guys. I am trying to read up on the past year. I want to get things running as well as I can before I bring over the other half of my hash.

I will take put in the above mentioned changes for bitcoin.conf. I have a feeling that leaving it open ended is taking up too much bandwith.

I'll do some research and find out what peers might be better. Where do you specify the list of peers?

I have not yet found the custom firmware for AntMiner S5 and S7. I didn't think it existed. If someone could point me there, I would appreciate.

windpath

legendary

Activity: 1258

Merit: 1027

Quote from: TTravis on November 20, 2015, 08:42:56 AM

I am up and running with p2pool now. Someone please check me out to see if everything looks good.

I have a Dell Percision 390 w/ 8GB memory and 250 GB SSD running latest bitcoin core and p2pool 14.0-25-g482f410.

bitcoin.conf has only three lines: server=1, rpcuser, and rpcpassword.

I am running on a T1 connection with everything connected to local node on network.
bitcoin client shows 42 active connections
p2pool shows 6 out, 2 in

Right now local rate shows 76 TH/s which is a little less that what I normally see on "that bug pool".

I have Antminers connected, all with standard firmware and settings. 3-S3's, 1-S4, and 77-S5's

I am looking for suggestions as to parameters for bitcoin.conf, or anything else that will help me run better.
Should I be looking at something called a relay node for better performance?

My p2pool address is: bitcoin.computing-management.com:9332

What would you do? Huh

Thanks,

Tom

Looking good Tom, congrats!

Everything looks pretty solid in your stats except for your efficiency.

It looks like you would benefit from finding some closer p2pool peers, your ping times are a little high and may be the cause of your orphaned shares: http://bitcoin.computing-management.com:9332/pings

Your getblocktemplate latency looks about normal, which would indicate that your bitcoin.conf may not be worth playing with. If you want to give it a try here are some pretty aggressive settings:

Code:

blockmaxsize=750000
mintxfee=0.0001
minrelaytxfee=0.0001
limitfreerelay=5
maxconnections=15

Matt's relay network certainly can not hurt, however it's slightly redundant in p2pool because the p2pool network is it's own relay network (thats why we have so few orphans).

Richy_T

legendary

Activity: 2576

Merit: 2267

1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k

Quote from: TTravis on November 20, 2015, 08:42:56 AM

I am up and running with p2pool now. Someone please check me out to see if everything looks good.

I have a Dell Percision 390 w/ 8GB memory and 250 GB SSD running latest bitcoin core and p2pool 14.0-25-g482f410.

bitcoin.conf has only three lines: server=1, rpcuser, and rpcpassword.

I am running on a T1 connection with everything connected to local node on network.
bitcoin client shows 42 active connections
p2pool shows 6 out, 2 in

Right now local rate shows 76 TH/s which is a little less that what I normally see on "that bug pool".

I have Antminers connected, all with standard firmware and settings. 3-S3's, 1-S4, and 77-S5's

I am looking for suggestions as to parameters for bitcoin.conf, or anything else that will help me run better.
Should I be looking at something called a relay node for better performance?

My p2pool address is: bitcoin.computing-management.com:9332

What would you do? Huh

Thanks,

Tom

If you go back the past few pages, there are some settings that should improve bitcoind's memory usage.

You might also consider upgrading to custom firmware on your miners. There are some changes that make things work better with p2pool. Details a few more pages back.

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