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

yslyung

legendary

Activity: 1500

Merit: 1002

Mine Mine Mine

Quote from: idonothave on October 21, 2015, 01:51:19 AM

Quote from: yslyung on October 21, 2015, 01:30:24 AM

here we go ! ...

BITCOIN BLOCK FOUND by 18oaD7wEawJPvTs9D1xfDorFXxTSm8p1WJ! @ 1267.51 GH/s

https://blockchain.info/block/00000000000000000d30874b7d3b90bda0fa939c86fd81349d0bb8d4fccdca2f

Quote from: midas28 on October 20, 2015, 10:45:51 PM

To anyone who has experiences in p2pool, for 2.3PH/s running 24x7 how many bitcoins would you estimate I would get/day?

Thanks

not that difficult to estimate ... if you are the only one running p2p with 2.3 PH then you would get all 25 btc rite ?

so now p2p is around 1.7ph + 2.3ph (yours) = 4 ph

math comes out to a little over 13 btc NOT daily. it is ONLY when p2p hits a block or more then you'll be rewarded with the btc which could be 4 a day too.

oh you do get a little "extra" bonus of 0.5% if you're the block finder.

i'd say give it a shot but you'll need lots of patience in p2p but it does pays off. ask away as many here would be able to give you answers to p2p.

to get 25 BTC per day you would need 4.4PHs. If you have 2.3PHs you will get daily 13 BTC. Actual luck is higher than 100%. 30 days luck is 147%. So ideal calculacion is 13*1.47=19.21BTC. My own 42 days back statistics says I have got around 120% of what I could mine with other pools. But for to reach this you need to have well done p2pool node (great hardware), well done bitcoind server, great internet connection, well tunned miners (spondoolies do not need any tunning, antminers do). good luck

That's a over estimation (don't forget to take the "dry spells" into account).

I'd rather NOT to over estimate the payout using history for future payout but use the history as payout reference/estimation based on a worse case scenario. just my 2 cents.

don't really need a good hw but of course it is preferred. maybe the correct term or word is "Proper Setup" hey but that's the fun of learning Wink

-bitcoind is bitcoind, i'm using qt on win7 & so far so good.
-great internet connection ? i'd say STABLE no need to be high speed or high bandwidth
-tuned miners ... hmm preferred of course but ant's do run fine some miners are NOT compatible though but should run. ask away & you shall get answers.

imho, there is no 1 single pool that's the best. all of it has it's up's & downs. be your own judge.

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

You can't use historical luck to determine future payout - that either ignorance of mathematics or deception.

Also the p2pool luck is over estimated by most sites coz it includes extra blocks but not the hashes that mined them - so yeah blocks with zero hashes will of course fake the luck up higher than it really is.
(The stale p2pool blocks that are valid blockchain blocks have no hash rate counted towards them in most stats anywhere)

idonothave

full member

Activity: 238

Merit: 100

Quote from: yslyung on October 21, 2015, 01:30:24 AM

here we go ! ...

BITCOIN BLOCK FOUND by 18oaD7wEawJPvTs9D1xfDorFXxTSm8p1WJ! @ 1267.51 GH/s

https://blockchain.info/block/00000000000000000d30874b7d3b90bda0fa939c86fd81349d0bb8d4fccdca2f

Quote from: midas28 on October 20, 2015, 10:45:51 PM

To anyone who has experiences in p2pool, for 2.3PH/s running 24x7 how many bitcoins would you estimate I would get/day?

Thanks

not that difficult to estimate ... if you are the only one running p2p with 2.3 PH then you would get all 25 btc rite ?

so now p2p is around 1.7ph + 2.3ph (yours) = 4 ph

math comes out to a little over 13 btc NOT daily. it is ONLY when p2p hits a block or more then you'll be rewarded with the btc which could be 4 a day too.

oh you do get a little "extra" bonus of 0.5% if you're the block finder.

i'd say give it a shot but you'll need lots of patience in p2p but it does pays off. ask away as many here would be able to give you answers to p2p.

to get 25 BTC per day you would need 4.4PHs. If you have 2.3PHs you will get daily 13 BTC. Actual luck is higher than 100%. 30 days luck is 147%. So ideal calculacion is 13*1.47=19.21BTC. My own 42 days back statistics says I have got around 120% of what I could mine with other pools. But for to reach this you need to have well done p2pool node (great hardware), well done bitcoind server, great internet connection, well tunned miners (spondoolies do not need any tunning, antminers do). good luck

idonothave

full member

Activity: 238

Merit: 100

Quote from: Richy_T on October 19, 2015, 12:59:39 AM

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.

I have found crossroads as a load balancer possible able to do this work. I am going soon to test running two bitcoind with two independent internet connections and let my p2pool node to be connected to them over crossroads.

yslyung

legendary

Activity: 1500

Merit: 1002

Mine Mine Mine

here we go ! ...

BITCOIN BLOCK FOUND by 18oaD7wEawJPvTs9D1xfDorFXxTSm8p1WJ! @ 1267.51 GH/s

https://blockchain.info/block/00000000000000000d30874b7d3b90bda0fa939c86fd81349d0bb8d4fccdca2f

Quote from: midas28 on October 20, 2015, 10:45:51 PM

To anyone who has experiences in p2pool, for 2.3PH/s running 24x7 how many bitcoins would you estimate I would get/day?

Thanks

not that difficult to estimate ... if you are the only one running p2p with 2.3 PH then you would get all 25 btc rite ?

so now p2p is around 1.7ph + 2.3ph (yours) = 4 ph

math comes out to a little over 13 btc NOT daily. it is ONLY when p2p hits a block or more then you'll be rewarded with the btc which could be 4 a day too.

oh you do get a little "extra" bonus of 0.5% if you're the block finder.

i'd say give it a shot but you'll need lots of patience in p2p but it does pays off. ask away as many here would be able to give you answers to p2p.

midas28

newbie

Activity: 23

Merit: 0

To anyone who has experiences in p2pool, for 2.3PH/s running 24x7 how many bitcoins would you estimate I would get/day?

Thanks

jtoomim

hero member

Activity: 818

Merit: 1006

Quote from: windpath on October 20, 2015, 03:03:32 PM

Hmmm, took a look, your right, at 2.5GB. Will have to investigate further tomorrow.

More info on this issue can be found on the bitcoin-dev and bitcoin-xt mailing lists:
http://bitcoin-development.narkive.com/j9BLYJIC/memory-leaks

windpath

legendary

Activity: 1258

Merit: 1027

Quote from: jtoomim on October 20, 2015, 02:01:33 PM

Quote from: windpath on October 20, 2015, 11:32:54 AM

On the mempool monitoring, it has grown to 11.5MB overnight, nothing to be overly concerned about yet, but will continue to keep an eye on it.

Code:

bitcoin-cli getmempoolinfo
{
"size" : 6090,
"bytes" : 11401452
}

No, this is not the right metric. The cases I've seen of bloated memory usage have been from something other than the mempool itself. My nodes typically have 2+ GB memory usage ("RSS") after a few days, but only 0.5 to 20 MB of mempool usage. You want to check the RSS using a program like top, or check /proc/$PID/status (Linux).

Hmmm, took a look, your right, at 2.5GB. Will have to investigate further tomorrow.

jtoomim

hero member

Activity: 818

Merit: 1006

Quote from: windpath on October 20, 2015, 11:32:54 AM

On the mempool monitoring, it has grown to 11.5MB overnight, nothing to be overly concerned about yet, but will continue to keep an eye on it.

Code:

bitcoin-cli getmempoolinfo
{
"size" : 6090,
"bytes" : 11401452
}

No, this is not the right metric. The cases I've seen of bloated memory usage have been from something other than the mempool itself. My nodes typically have 2+ GB memory usage ("RSS") after a few days, but only 0.5 to 20 MB of mempool usage. You want to check the RSS using a program like top, or check /proc/$PID/status (Linux).

jonnybravo0311

legendary

Activity: 1344

Merit: 1024

Mine at Jonny's Pool

Quote from: Polyatomic on October 20, 2015, 12:54:51 AM

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

...
I watched as the bitcoind would slowly consume more and more memory, up until it took almost the entire 8G available, at which point it would invariably die off.

What was the magic you used to produce the output, (8G <-- bitcoind is using this much ram.)
Somethings not right there man.

Linux will try to use alot of the computers memory to keep the system fast. 8 gigs of ram
i'm thinking is below average for power linux users. Is adding more of it an option for you.

Maybe i'll bootstrap a build and run the latest bitcoind and the p2pool to see what the story is.

No magic at all... and honestly I'm not sure why things just kept spiraling up like they did. I had that node running for over a year and never experienced any problems with it until relatively recently. I ended up just killing the node. I couldn't justify the $80 a month expense, and I didn't have the time to constantly monitor it to ensure it was behaving. I know there are plenty of other nodes out there running on Linux, and likely not experiencing anything near what I saw, and to be honest I never bothered inspecting it too closely. I just finally got fed up with the hassle and realized that I didn't want to deal with it any longer. I still run my own local node and now use windpath's node as my backup instead of my own VPS.

windpath

legendary

Activity: 1258

Merit: 1027

Quote from: p3yot33at3r on October 20, 2015, 06:48:16 AM

@ windpath: Are the luck stats displayed on your web GUI correct?:

They are not 100% accurate, but about as good as we can get with the data available.

The global hashrate reported by any p2pool node is an estimate based on difficulty and submitted shares pool wide, so expected time to block is not perfect.

If you dig back in the thread when I was developing the front end I published the formula used and how it was calculated for feedback and made some tweaks.

Quote from: p3yot33at3r on October 20, 2015, 06:48:16 AM

If they are, I'm pretty sure there isn't another pool out there that can touch us atm

I agree 100%. Even when our luck is down I still think P2Pool is by far the best option for miners.

- Trustless & Decentralized
- Highly resistant to DDOS attacks
- 100% Uptime if p2pool backup nodes are used (best use for my node)
- Lowest orphan rate of any pool, period.
- Open source
- No registration of any kind
- I could go on and on, but I think you get it already Wink

On the mempool monitoring, it has grown to 11.5MB overnight, nothing to be overly concerned about yet, but will continue to keep an eye on it.

Code:

bitcoin-cli getmempoolinfo
{
"size" : 6090,
"bytes" : 11401452
}

Richy_T

legendary

Activity: 2576

Merit: 2267

1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k

Quote from: p3yot33at3r on October 20, 2015, 09:01:00 AM

Not very helpful or fun to do, I know - but that's what I'd do....... Tongue

But my understanding is that even if one fully disconnects from p2pool, the shares you've found should count for 24 hours from their time of creation. Once those shares are in the p2pool net, it shouldn't matter my setup.

Personally, I'm a casual miner and this has only cost me a couple of $ worth of Bitcoin so I'm not going to sweat it too much unless it keeps happening but I'm willing to give back in terms of assisting troubleshooting.

p3yot33at3r

sr. member

Activity: 266

Merit: 250

Quote from: Richy_T on October 20, 2015, 08:48:56 AM

Any other input on this? If shares are being dropped early, it seems like this is either a bug that is causing it or a bug that is being exploited by a malicious actor (?). Either way, not good. I'm willing to help with diagnosing this if anyone who knows what they're doing is interested. I suspect it's easy enough to duplicate.

I'm pretty sure it's not a p2pool issue, otherwise we'd all be suffering from it? So, that leaves either a malicious 3rd party or it's a problem with the users setup. My diagnostic skills are fairly limited I'm afraid - so I won't be much help. If it were me who was having this problem, I'd consider ensuring my rig has all the right security settings set up correctly first (firewall, ports, iptables etc), then I'd start from scratch & check all my configs, redownload/recompile everything & see if the issue persists.

Not very helpful or fun to do, I know - but that's what I'd do....... Tongue

Richy_T

legendary

Activity: 2576

Merit: 2267

1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k

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)?

Any other input on this? If shares are being dropped early, it seems like this is either a bug that is causing it or a bug that is being exploited by a malicious actor (?). Either way, not good. I'm willing to help with diagnosing this if anyone who knows what they're doing is interested. I suspect it's easy enough to duplicate.

p3yot33at3r

sr. member

Activity: 266

Merit: 250

I'm having no issues with my node, in fact, I'm really happy with how it & p2pool are performing in general - especially since I reverted back to the standard bitcoind settings - latency has reduced nicely.

@ windpath: Are the luck stats displayed on your web GUI correct?:

Seven Days 162.74%
Thirty Days 148.03%

If they are, I'm pretty sure there isn't another pool out there that can touch us atm

Polyatomic

sr. member

Activity: 257

Merit: 250

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

...
I watched as the bitcoind would slowly consume more and more memory, up until it took almost the entire 8G available, at which point it would invariably die off.

What was the magic you used to produce the output, (8G <-- bitcoind is using this much ram.)
Somethings not right there man.

Linux will try to use alot of the computers memory to keep the system fast. 8 gigs of ram
i'm thinking is below average for power linux users. Is adding more of it an option for you.

Maybe i'll bootstrap a build and run the latest bitcoind and the p2pool to see what the story is.

jonnybravo0311

legendary

Activity: 1344

Merit: 1024

Mine at Jonny's Pool

Quote from: jtoomim on October 19, 2015, 05:43:10 PM

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.

Are both bitcoind nodes being used for p2pool? My testing indicates that the use of getblocktemplate is necessary for the memory leaking to occur.

Yes. I was running a VPS (a DigitalOcean droplet) that I used as my backup p2pool node. I had other miners besides my own on it pretty constantly. It ran for quite a long time until a few weeks ago it started acting up. The bitcoind process would die for no apparent reason. Sometimes the p2pool process would just die off as well. Finally spending time looking at the box, I watched as the bitcoind would slowly consume more and more memory, up until it took almost the entire 8G available, at which point it would invariably die off.

On my Mac, I also run a p2pool node that is local to my miners at my home. That bitcoind, just like the one on my droplet, was compiled from source. On my local node, I've never seen it utilize more than 1G of RAM. More typically, it's around 400-500MB. Granted, I have fewer miners on my local home node (2-3 at most with a total hash of about 5TH/s). On my Linux node, I typically had 5-6 miners with a hash rate of about 15TH/s.

Meuh6879

legendary

Activity: 1512

Merit: 1012

[HS]
i have opened a thread for the memory (and CPU) problem.
https://github.com/bitcoinxt/bitcoinxt/issues/82

every day, i change the maxmempooltx after viewing the history of the CPU (less 100% freeze = increase the setting).

actually, it fluctuate from 800 to 1200.
[/HS]

This problem impact RPC server ... and so, the P2Pool process.

jtoomim

hero member

Activity: 818

Merit: 1006

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.

Are both bitcoind nodes being used for p2pool? My testing indicates that the use of getblocktemplate is necessary for the memory leaking to occur.

jonnybravo0311

legendary

Activity: 1344

Merit: 1024

Mine at Jonny's Pool

Quote from: windpath on October 19, 2015, 01:22:24 PM

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.

If I remember that UI correctly, there's a config file that defines the stats refresh rate, which defaults to like 10 seconds for the stats and 30 for the graphs (or something like that). Of course, you've customized it so much that file has probably been rendered irrelevant at this point Tongue

.

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