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

[Sanweb40]

Give it a methode by P2Pool to adjust the shares for PPLNS?

[1713955341]

1713955341

[1713955341]

1713955341

[1713955341]

1713955341

[forrestv]

Give it a methode by P2Pool to adjust the shares for PPLNS?

You mean the N in PPLNS? Number of shares? That's hard-coded to 3 block-equivalents of shares. Why would you want to adjust it?

[zvs]

Indeed situation has been improved since commit
At the day of patch release, p2pool was on 36 TH/s with 161k share diff. Right now it's on 50.6 TH/s with 171k share diff. That's 40% hashrate increase with only 6% sharediff increase. Very nice surprise for small miners But we need more people to upgrade, so variance for small miners will go down even further. Please upgrade!

Is the hash rate increase due to multipool.us hooking up to p2pool? Or does it not show on the p2pool graph?

It likely is.
Their address is 146197ntzrBT41DDQRrB2STBb19dw7ct2F, the highest hashrate of all miners.

it's only at 90% efficiency, hoho

[RoadTrain]

Indeed situation has been improved since commit
At the day of patch release, p2pool was on 36 TH/s with 161k share diff. Right now it's on 50.6 TH/s with 171k share diff. That's 40% hashrate increase with only 6% sharediff increase. Very nice surprise for small miners But we need more people to upgrade, so variance for small miners will go down even further. Please upgrade!

Is the hash rate increase due to multipool.us hooking up to p2pool? Or does it not show on the p2pool graph?

It likely is.
Their address is 146197ntzrBT41DDQRrB2STBb19dw7ct2F, the highest hashrate of all miners.

it's only at 90% efficiency, hoho

Maybe point this to them? If you know of a way to improve efficiency.

[zvs]

Indeed situation has been improved since commit
At the day of patch release, p2pool was on 36 TH/s with 161k share diff. Right now it's on 50.6 TH/s with 171k share diff. That's 40% hashrate increase with only 6% sharediff increase. Very nice surprise for small miners But we need more people to upgrade, so variance for small miners will go down even further. Please upgrade!

Is the hash rate increase due to multipool.us hooking up to p2pool? Or does it not show on the p2pool graph?

It likely is.
Their address is 146197ntzrBT41DDQRrB2STBb19dw7ct2F, the highest hashrate of all miners.

it's only at 90% efficiency, hoho

Maybe point this to them? If you know of a way to improve efficiency.

I didn't snoop around & couldn't see an easy way to get the list of peers he's connected to & how many (outgoing/incoming) & where his shares are coming from atm, so not sure

ed: oh, not sure what the sample size is either, it could just be luck & getting a lot of shares directly before a new block hits the network

good example being 195.72.200.193's two orphans

[zkfq123]

how to setup difficult with my avalon 116g ？

should be "wallet/1000+ 116 "?

who can help me?thanks

[lenny_]

how to setup difficult with my avalon 116g ？

should be "wallet/1000+ 116 "?

who can help me?thanks

Just:

Code:

btcaddress+256

Should be ok.

[zvs]

zut alors!

Pool Luck(?) (7 days, 30 days, 90 days): 142.3%113.5%109.1%

[zvs]

so many orphans for building off a block that came 2 seconds later...

some ppl need to fix bitcoind connections too 

[zkfq123]

Code:

btcaddress+256

Should be ok.
[/quote]
thanks a lot,but i dont understand,why is

Code:

btcaddress+256

and
if i have another  82g avalon i also use btcaddress+256 ?

[rav3n_pl]

Add +number after ur adddress, where number is double ur rate in Gh/s.
If you have 30GH/s use +64 if 100 use +256
This will lower traffic u`re sending to pool and it will decrease cpu usage of node also.
If you mine few machines on one address and one node sum Gh/s of all machines.

[wtogami]

https://bitcointalk.org/index.php?topic=329860
November 8th, 2013, the Litecoin Dev Team awarded a ~$2,000 grant to Forrest Voight in support of development to improve the scalability of the p2pool decentralized mining network.  Please read the thread for more details.

[Polyatomic]

Can we possibly have a standard operating procedure regarding , host requirements and node installation , tips to help people run on p2pool as efficiently as possible. Is my GBT latency too high ? Does it matter ? Why it matters. My node shows X kb incoming X kb outgoing , is that ideal ? , if not why. Do I need lots of RAM and unlimited bandwidth.



Here is a snapshot of my rig on p2pool , can I do anything to improve my efficiency.

[zvs]

Can we possibly have a standard operating procedure regarding , host requirements and node installation , tips to help people run on p2pool as efficiently as possible. Is my GBT latency too high ? Does it matter ? Why it matters. My node shows X kb incoming X kb outgoing , is that ideal ? , if not why. Do I need lots of RAM and unlimited bandwidth.



Here is a snapshot of my rig on p2pool , can I do anything to improve my efficiency.

Is that a local p2pool?  Is all the DOA caused by the specific ASIC equipment?  I can mine to remote host (~200ms to Germany) and get about 1-2% DOA, w/ vid card (200ms flat should average out to less than 1% DOA (.667%), but you have some local & remote delay, maybe multiple workers, etc)..  an overloaded CPU could cause more DOA also

i think you got lucky with zero orphans and just 6 outgoing connections, unless maybe those 6 outgoing connections were handpicked by you... re:  set the max outgoing to zero and using --p2pool-node for all 6

[zvs]

p2pool problem:

People see this 20% DOA/stale shit and are like "OMG, 20% less monies!1", instead of saying 'lol, someone has some shitty setup that's improving my relative efficiency, they are losing hundreds of thousands of ugandan dollars'.    too bad that in the long run, you want people to not be dumb and be able to set up p2pool properly.

tip #1:  TI-99's and Commodore 64's are not adequate to run p2pool servers on.  either spend a couple hundred bucks getting a subpar computer that can run p2pool decently, pay $10 or $20 to OVH for server hosting, or (gasp) mine on a remote server.  there are plenty out there that are at 0%.  mine is at 1%, but that 80% efficiency you're getting to your Commodore is a lot worse than paying a 1% fee.  try http://p2pool-nodes.info/ and http://p2pool.hostv.pl/

tip #2:  

run p2pool with

./run_p2pool.py (any other flags) --p2pool-node 5.9.24.81 --p2pool-node 198.12.127.2 --p2pool-node 64.120.253.194 --outgoing-conns 5

that means if all 3 of those servers are up (and not full on incoming connections, being DDoSed, DoSed, or being raided by the Interpol for stealing massive amounts of bitcoins), you'll have 8 outgoing connections.  if none are up, you'll have 5.  default is 6.  that's not bad, right?   if you have enough bandwidth, then allow some incoming connections.  i think 40 is too much, but 20-25 is ok.

tip #3:  after about 30 minutes, look at your share history.  see which nodes you're actually receiving shares from.  if they're incoming connections, test port 9333 by trying to telnet to it first.  include those in your --p2pool-node list.  


tip #4:  high getblocktemplate latency isn't a huge deal...  except it's symptomatic of also having horrible performance issues, probably either RAM or CPU related and also often caused by having an old version of bitcoind, filled with horse staple battery transactions.  migrate off of the Atari 400 and/or fix your bitcoind, and/or reduce maxblocksize from 1000000 to 500000 or 250000.

tip #5:  use xxx:9332/pings .. if someone is at 2000ms latency, then either their bandwidth is saturated or their Amiga is having issues.  tcpkill them for a new connection..  somewhat related, use xxx:9332/peer_txpool_sizes to see all the people that are trying to help out horse staple battery get those transactions processed

tip #6: don't pay 2% fees to a pool with 70% efficiency

aha!  forgot to mention bitcoind

tip #7: compile bitcoind with outgoing connections of 1, run bitcoind with listen=1, maxconnections=2, with one node on connect... well, that's what I do, since I can monitor it constantly.. you'd probably want to change maxconnections to 3 or 4, in case one of the nodes craps out, be it due to the Interpol, cult of the dead cow, or whatever else.  an example conf file,

server=1
daemon=1
rpcuser=bleat
rpcpassword=bleatbleat
#datadir=/home/zevus/ramdisk
maxconnections=2
rpcallowip=127.0.0.1
rpcport=31337
port=31338
#timeout=150
#dbcache=xxx
par=8
listen=1       (<--- necessary cause of p2pool)
gen=0
upnp=0
keypool=0  (you don't store bitcoins on this wallet, right?  right?)
dns=0
detachdb=1
logtimestamps=1
bantime=30
banscore=501
#blockminsize=0
#blockprioritysize=0
blockmaxsize=250000

#Myself
connect=5.9.24.81
#connect=198.12.127.2
#connect=64.120.253.194

..... now, I don't think w/o compiling it yourself you can modify the 8 outgoing connections?  i think in that case, maxconnections of 9, listen=1, and just using 'connect' and firewalling the incoming bitcoind port would still work?  it's not supposed to connect to other nodes, anyway...  (besides the one you use connect= on, which is the difference between that and addnode)

ed: fixed --max-outgoing to real flag of --outgoing-conns

[Polyatomic]

Cheers for taking the time for to write that up zvs. It helps  to learn from others with experience.

[HellDiverUK]

either their bandwidth is saturated or their Amiga is having issues.  

Impossible.  Amigas never have issues.  Until the Guru Meditation arrives.

[zvs]

Cheers for taking the time for to write that up zvs. It helps  to learn from others with experience.

Now if people will do it... =p

Also, you might have high latency to those three p2pools I suggested to --addnode, just look at the list on http://p2pool-nodes.info/ and find some other well connected ones if so.  I wouldn't add any w/ an average getblocktemplate time of over .3s, since those are probably overloaded as is... well, either that, or they may be experiencing this issue (as referenced above):



immediate action is recommended in such cases

... and I thought I'd add that most orphans directly after a block is solved are unavoidable, as p2pool will (usually) orphan the share that was directly before the block solve (or it may have been a few seconds after, which is the reason for it doing that... but 95% of the time it's a legit share that just gets jacked). 

[jedimstr]

I've seen various suggestions for setting up workers with p2pool, but want to better understand the 3 main paths I've seen so far.

What are the relative Advantages and Disadvantages to the following for the Miner? The local Pool? the P2Pool Network as a whole?
Using 15Ghs as an example...

Method 1: add +N to worker address where N = double your miner's hashrate
Example: worker_address+30
Adv/Disadv - Miner?
Adv/Disadv - Local Pool?
Adv/Disadv - P2Pool Network?

Method 2: add /N+1 to worker address where N = 210xHashrate
Example: worker_address/3150+1
Adv/Disadv - Miner?
Adv/Disadv - Local Pool?
Adv/Disadv - P2Pool Network?

Method 3: just use worker_address
Example: worker_address
Adv/Disadv - Miner?
Adv/Disadv - Local Pool?
Adv/Disadv - P2Pool Network?


I've been using Method #2 for awhile to supposedly help lower speed miners while keeping P2Pool shares flowing with P2Pool diff 1 work, but my understanding on this may not be right.

[zvs]

I've seen various suggestions for setting up workers with p2pool, but want to better understand the 3 main paths I've seen so far.

What are the relative Advantages and Disadvantages to the following for the Miner? The local Pool? the P2Pool Network as a whole?
Using 15Ghs as an example...

Method 1: add +N to worker address where N = double your miner's hashrate
Example: worker_address+30
Adv/Disadv - Miner?
Adv/Disadv - Local Pool?
Adv/Disadv - P2Pool Network?

Method 2: add /N+1 to worker address where N = 210xHashrate
Example: worker_address/3150+1
Adv/Disadv - Miner?
Adv/Disadv - Local Pool?
Adv/Disadv - P2Pool Network?

Method 3: just use worker_address
Example: worker_address
Adv/Disadv - Miner?
Adv/Disadv - Local Pool?
Adv/Disadv - P2Pool Network?


I've been using Method #2 for awhile to supposedly help lower speed miners while keeping P2Pool shares flowing with P2Pool diff 1 work, but my understanding on this may not be right.

bitcoinaddress/x+y

Yeah, the x variable wouldn't do anything unless it was over the base share difficulty which is at 216k right now.  At 15ghash, you shouldnt increase that unless, eh, you're feeling really lucky.  Would have to be over 216,000 to have any impact ..

The Y amount is just used to calculate your hashrate on the webpage.  With pushpool it mattered a lot more, with stratum it doesn't really matter much.  I guess it consumes a little more bandwidth if you're using 1 share difficulty instead of 10-20.  You might as well use the higher #...