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

windpath

legendary

Activity: 1258

Merit: 1027

Quote from: jonnybravo0311 on October 19, 2015, 01:12:56 PM

I'm inclined to believe the memory leak... although I've only seen it on my Linux (Ubuntu 14.04) node. I watched bitcoind spool up to consume 8GB of RAM before it was shut down. On my Mac, using the same codebase, I regularly only see about 400MB of RAM being consumed by the bitcoind. Both Linux and Mac are built from source.

Anyway, back on topic... I wonder why my reject rate is always so high mining on your node windpath. My ping time to your server is about 17ms, yet I'm constantly seeing 10% or higher DOA. When I was running my own VPS node (with about the same ping time), I would typically see about 3-4%. Yes, running my own local node when I'm at home is considerably lower (usually about 1% or less), and that's to be expected since my miners and my node are all hardwired into the same internal gigabit network.

I'm wondering if it is caused by the traffic on the node, and p2pool's inherent single-threaded execution. Anyone have thoughts on it?

Yea, I'll keep an eye on it, so far mempool seems to be behaving normally.

As to the high reject rate on my node I suspect you are correct.

In addition to the # of miners a lot of folks seem to park their browsers on the stats pages which hit both p2pool and bitcoind to pull some of the data for the front end.

There are some relatively easy fixes like setting the data refresh to stop in the browser after say 30 minutes with a "I'm still here" button to restart it....

I'll look into it.

jonnybravo0311

legendary

Activity: 1344

Merit: 1024

Mine at Jonny's Pool

Quote from: windpath on October 19, 2015, 11:18:39 AM

Quote from: jtoomim on October 19, 2015, 09:40:10 AM

Quote from: windpath on October 19, 2015, 08:17:06 AM

Not sure what went down, something crashed bitcoind, which is unusual on my server.

The congested mempool that we've had recently from the 14kB blocks is causing excessive memory consumption. From my investigation so far, it looks like there's a memory leak in getblocktemplate/CreateNewBlock. This makes bitcoind's memory consumption increase by as much as 1 GB per day. I've been restarting my bitcoind processes every 2 days or so.

We keep relatively strict limits for bitcoind's mempool on the node, granted below is only since this mornings restart, I'll keep an eye on it.

Code:

bitcoin-cli getmempoolinfo
{
    "size" : 1967,
    "bytes" : 1745856
}

I'm inclined to believe the memory leak... although I've only seen it on my Linux (Ubuntu 14.04) node. I watched bitcoind spool up to consume 8GB of RAM before it was shut down. On my Mac, using the same codebase, I regularly only see about 400MB of RAM being consumed by the bitcoind. Both Linux and Mac are built from source.

Anyway, back on topic... I wonder why my reject rate is always so high mining on your node windpath. My ping time to your server is about 17ms, yet I'm constantly seeing 10% or higher DOA. When I was running my own VPS node (with about the same ping time), I would typically see about 3-4%. Yes, running my own local node when I'm at home is considerably lower (usually about 1% or less), and that's to be expected since my miners and my node are all hardwired into the same internal gigabit network.

I'm wondering if it is caused by the traffic on the node, and p2pool's inherent single-threaded execution. Anyone have thoughts on it?

windpath

legendary

Activity: 1258

Merit: 1027

Quote from: jtoomim on October 19, 2015, 09:40:10 AM

Quote from: windpath on October 19, 2015, 08:17:06 AM

Not sure what went down, something crashed bitcoind, which is unusual on my server.

The congested mempool that we've had recently from the 14kB blocks is causing excessive memory consumption. From my investigation so far, it looks like there's a memory leak in getblocktemplate/CreateNewBlock. This makes bitcoind's memory consumption increase by as much as 1 GB per day. I've been restarting my bitcoind processes every 2 days or so.

We keep relatively strict limits for bitcoind's mempool on the node, granted below is only since this mornings restart, I'll keep an eye on it.

Code:

bitcoin-cli getmempoolinfo
{
    "size" : 1967,
    "bytes" : 1745856
}

Richy_T

legendary

Activity: 2576

Merit: 2267

1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k

Quote from: jtoomim on October 19, 2015, 09:41:47 AM

Quote from: Richy_T on October 18, 2015, 11:23:21 PM

This is what I'm talking about.

If it's shares over the last 24 hours, surely the payout should drop slowly as old shares expire (which it seems to do on Fri 16th to Sat 17th)?

That looks like the default payout address used by that node was changed. The graph shows the payout for the address that was being used at the time the data point was collected, not at the time the graph was generated.

It does look that way but is definitely not the case. p2pool has been running since Oct16 with the same address...

user 1677 1668 15 Oct16 pts/3 09:28:11 python ./run_p2pool.py -a 1address

What happened was that someone was saturating my upstream by with a bitcoind connection (presumably downloading the blockchain). I ran a tc.sh script which was apparently over-conservative with the bandwidth settings (both for bitcoind and p2pool). I can understand why that would stop me getting new shares but not that precipitous drop.

jtoomim

hero member

Activity: 818

Merit: 1006

Quote from: yslyung on October 19, 2015, 03:10:01 AM

yeah another block, more pls to cover the dry spell.

http://173.48.117.206:9332/static/graphs.html?Day

This one was found by a 5 TH/s miner.

jtoomim

hero member

Activity: 818

Merit: 1006

Quote from: Richy_T on October 18, 2015, 11:23:21 PM

This is what I'm talking about.

If it's shares over the last 24 hours, surely the payout should drop slowly as old shares expire (which it seems to do on Fri 16th to Sat 17th)?

That looks like the default payout address used by that node was changed. The graph shows the payout for the address that was being used at the time the data point was collected, not at the time the graph was generated.

jtoomim

hero member

Activity: 818

Merit: 1006

Quote from: windpath on October 19, 2015, 08:17:06 AM

Not sure what went down, something crashed bitcoind, which is unusual on my server.

The congested mempool that we've had recently from the 14kB blocks is causing excessive memory consumption. From my investigation so far, it looks like there's a memory leak in getblocktemplate/CreateNewBlock. This makes bitcoind's memory consumption increase by as much as 1 GB per day. I've been restarting my bitcoind processes every 2 days or so.

windpath

legendary

Activity: 1258

Merit: 1027

Quote from: yslyung on October 19, 2015, 03:10:01 AM

windpath, your site is partially working ? seems like it may not be updating.

yeah another block, more pls to cover the dry spell.

Thanks,

Not sure what went down, something crashed bitcoind, which is unusual on my server.

Restarted, will keep an eye on it today.

yslyung

legendary

Activity: 1500

Merit: 1002

Mine Mine Mine

windpath, your site is partially working ? seems like it may not be updating.

yeah another block, more pls to cover the dry spell.

Richy_T

legendary

Activity: 2576

Merit: 2267

1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k

Quote from: idonothave on October 19, 2015, 12:33:44 AM

you mean this one http://lnlb.sourceforge.net/ for example?

Maybe. I don't know enough about it. I would imagine that p2pool talking to bitcoind is simple enough that simple load balancing would be enough but I don't know enough to say for sure.

idonothave

full member

Activity: 238

Merit: 100

Quote from: Richy_T on October 18, 2015, 04:23:18 PM

Quote from: idonothave on October 18, 2015, 02:03:12 PM

question was: Have one p2pool process connecting to multiple bitcoind processes via RPC at the same time?
you have answered: No.
how should I undersand this: [BITCOIND_RPCUSERPASS [BITCOIND_RPCUSERPASS ...]]

Fallback option?

You might be able to connect to multiple bitcoinds with a load balancer, maybe.

you mean this one http://lnlb.sourceforge.net/ for example?

Richy_T

legendary

Activity: 2576

Merit: 2267

1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k

This is what I'm talking about.

If it's shares over the last 24 hours, surely the payout should drop slowly as old shares expire (which it seems to do on Fri 16th to Sat 17th)?

Richy_T

legendary

Activity: 2576

Merit: 2267

1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k

Any idea why payouts drop off so precipitously when I have any issues with my setup. I mean, obviously the payout builds up slowly over time but surely they should drop of at a similar rate? I made some changes which apparently stopped p2pool from producing valid shares then shortly after that, my potential payout dropped from near .025 btc to around .002 in almost no time.

windpath

legendary

Activity: 1258

Merit: 1027

Haha! Nice call... But even then keeping your power consumption and heat output low enough to be undetectable from outside your house might prove to be challenging... Wink

Richy_T

legendary

Activity: 2576

Merit: 2267

1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k

Quote from: windpath on October 18, 2015, 08:22:09 PM

If your mining on your own public node then it's IP is traceable, if your mining on someone else's node then they can see your miners IP... The latency introduced by using VPN or Tor will kill most of your shares...

That being said its about as anonymous as you can get until you spend the coins, then the recipient can easily tell they are fresh P2Pool block reward coins and depending on what you buy will most likely need some kind of contact info for you. You could mix them first if your really paranoid...

I'd say overall P2Pool is highly private, but like with anything else bitcoin only truly anonymous if you follow strict and comprehensive practices to avoid identity disclosure from day 1.

So what I'm hearing is: Mine on your neighbor's wifi Wink

windpath

legendary

Activity: 1258

Merit: 1027

If your mining on your own public node then it's IP is traceable, if your mining on someone else's node then they can see your miners IP... The latency introduced by using VPN or Tor will kill most of your shares...

That being said its about as anonymous as you can get until you spend the coins, then the recipient can easily tell they are fresh P2Pool block reward coins and depending on what you buy will most likely need some kind of contact info for you. You could mix them first if your really paranoid...

I'd say overall P2Pool is highly private, but like with anything else bitcoin only truly anonymous if you follow strict and comprehensive practices to avoid identity disclosure from day 1.

p3yot33at3r

sr. member

Activity: 266

Merit: 250

Quote from: Richy_T on October 18, 2015, 06:17:10 PM

Quote from: p3yot33at3r on October 18, 2015, 06:12:19 PM

Quote from: Richy_T on October 18, 2015, 04:27:42 PM

Edit: Nevermind. Blockchain timestamp is UTC. The time difference takes care of some of that. Close enough. Next block, please.

One of the many beauties of p2pool - payments are always correct & always paid. No reliance on any middleman & no chance of being conned

And no chain of ownership

Though it surely is not completely anonymous. Just how traceable is p2pool?

All coins mined by p2pool are freshly minted virgin coins. No history at all. Anyone can see to what address the payments have gone to of course, if that's what you mean.

Richy_T

legendary

Activity: 2576

Merit: 2267

1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k

Quote from: p3yot33at3r on October 18, 2015, 06:12:19 PM

Quote from: Richy_T on October 18, 2015, 04:27:42 PM

Edit: Nevermind. Blockchain timestamp is UTC. The time difference takes care of some of that. Close enough. Next block, please.

One of the many beauties of p2pool - payments are always correct & always paid. No reliance on any middleman & no chance of being conned

And no chain of ownership

Though it surely is not completely anonymous. Just how traceable is p2pool?

p3yot33at3r

sr. member

Activity: 266

Merit: 250

Quote from: Richy_T on October 18, 2015, 04:27:42 PM

Edit: Nevermind. Blockchain timestamp is UTC. The time difference takes care of some of that. Close enough. Next block, please.

One of the many beauties of p2pool - payments are always correct & always paid. No reliance on any middleman & no chance of being conned

Richy_T

legendary

Activity: 2576

Merit: 2267

1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k

Quote from: jtoomim on October 18, 2015, 10:13:33 AM

New block. Thanks Cryptal.

http://btcpool.cryptal.net:9332/static/share.html#0000000000000000037433dd74c771d11a0ab32c274069a52b225080c47001c6

The miner that found it has 2 TH/s.

Hmm, my payout is about 1/10 of what my graph shows it should be...

Graph shows ~0.02, payout was <0.002

Edit: Nevermind. Blockchain timestamp is UTC. The time difference takes care of some of that. Close enough. Next block, please.

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