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

smooth

legendary

Activity: 2968

Merit: 1198

Quote from: nreal on January 20, 2014, 09:08:05 AM

Its impossible to try to get the best out of p2pool with lets say 120gh when you get from 0 to 3 shares a day.

0-3 shares per day is just fine. The shares are active for a day and a half, so almost every single day you will have one or more shares working. Your daily earnings will fluctuate but only rarely to zero and over relatively few days it will average out.

With a much lower hash rate like 10 GH you could make the argument it will take much longer to average out, although I still maintain at that point the numbers are so small the variance doesn't matter. If you get $0 instead of $1 on one day and get $2 instead of $1 on another day you're not going to go bankrupt over it.

ksenter

member

Activity: 90

Merit: 10

Quote from: mdude77 on January 18, 2014, 06:50:16 PM

Just for comparison... since the common belief is that the high variance and high share difficulty doesn't affect your payout, let's compare.

I have 38GH/s. It's a cube, I brought it online almost 13 days ago, pointing to BTC Guild. Since then my total payout has been 0.12764. According to BTCGuild stats, we're at 99.7% luck for the last 14 days, so I'm pretty close to "average" payout. I'm not counting the ~0.21 NMC I've earned.

Can someone who has significantly larger hashrate post their comparison? Ie, what you made in the last 13 days scaled down to 38GH/s?

EDIT: I'd also like to see someone who has an equivalent hashrate or less.

M

January 6-18 with my 30GH I got 0.1261. But I don't think that's the best representation. Lets check again when you have a longer period. There was a few days where I got 0 and then a short period where I got an abnormally large payout. I know variance is normal but this was the most extreme I'd seen up to this point.

bkminer

full member

Activity: 216

Merit: 100

Don't let the nam-shub in your operating system.

Is anyone else seeing errors in the p2pool log when they hit the graphs.html page?

Code:

2014-01-20 11:31:31.292469 > Error in DeferredResource handler:
2014-01-20 11:31:31.292658 > Traceback (most recent call last):
2014-01-20 11:31:31.292756 > File "/home/rick/p2pool/p2pool/util/deferred_resource.py", line 24, in render
2014-01-20 11:31:31.292832 > defer.maybeDeferred(resource.Resource.render, self, request).addCallbacks(finish, finish_error)
2014-01-20 11:31:31.292915 > File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 134, in maybeDeferred
2014-01-20 11:31:31.292987 > result = f(*args, **kw)
2014-01-20 11:31:31.293057 > File "/usr/lib/python2.7/dist-packages/twisted/web/resource.py", line 216, in render
2014-01-20 11:31:31.293172 > return m(request)
2014-01-20 11:31:31.293245 > File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1181, in unwindGenerator
2014-01-20 11:31:31.293319 > return _inlineCallbacks(None, gen, Deferred())
2014-01-20 11:31:31.293407 > --- ---
2014-01-20 11:31:31.293482 > File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1039, in _inlineCallbacks
2014-01-20 11:31:31.293569 > result = g.send(result)
2014-01-20 11:31:31.293658 > File "/home/rick/p2pool/p2pool/web.py", line 189, in render_GET
2014-01-20 11:31:31.293748 > res = yield self.func(*self.args)
2014-01-20 11:31:31.293826 > File "/home/rick/p2pool/p2pool/web.py", line 444, in
2014-01-20 11:31:31.293913 > new_root.putChild('graph_data', WebInterface(lambda source, view: hd.datastreams[source].datavie ws[view].get_data(time.time())))
2014-01-20 11:31:31.293993 > exceptions.KeyError: 'last_Hour'

Edit: my lack of python experience, which I will have to fix

oldbushie

member

Activity: 94

Merit: 10

When is it safe to try removing --max-conns=0?

alanwgeorge

newbie

Activity: 16

Merit: 0

Quote from: forrestv on January 19, 2014, 05:53:12 PM

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Downloaded latest: git clone https://github.com/forrestv/p2pool.git

Been up for about 16 hours now. Had one incident about an hour in, but it's been clean since then.

Thanks!
-alan

nreal

full member

Activity: 932

Merit: 100

arcs-chain.com

Quote from: mdude77 on January 20, 2014, 08:54:27 AM

Quote from: zvs on January 20, 2014, 07:33:37 AM

The pool I ran for bitcoins averaged ~110-115% efficiency, but that was on a dedicated server (not a VPS) in Germany with 1gbit/1gbit switch (200mbps guaranteed but in practice could 99% of the time get 80MB/s + ). Averaged around 3-5% DOA for me and about 2-4% orphans.

When I initially tried to set up my home connection, I was getting around 0-1% DOA and 15-20% orphans. A few percentage of the orphan rate was from being in the US instead of France/Germany/Netherlands where most of these dedicated servers & VPS are running. Most was from my 768kbps upstream cap.

Later on I was able to set it up w/ 0-1% DOA and an orphan rate under 10% (though it still wasn't as good as just using German remote server, after share time got changed to 30s)... anyway, the deal is, just have bitcoind connect to 1 or 2 servers & also your p2pool node need only connect to a handful of servers... you just have to pick the right ones. I have no clue what those are anymore. (ie, change outgoing connections to 0 and handpick the servers to connect to)

ed: i think you can find a VPS for a couple of bucks to run a bitcoind relay on

That's a decent idea about running a VPS for a bitcoind relay. I could stick p2pool on there too while I'm at it.

It still doesn't solve the high share difficulty problem though.

M

Youre right on this, and because sharedif is so high - there will be less and less new users. Its impossible to try to get the best out of p2pool with lets say 120gh when you get from 0 to 3 shares a day.

Sad but this is it. Or is this shit.

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: zvs on January 20, 2014, 07:33:37 AM

The pool I ran for bitcoins averaged ~110-115% efficiency, but that was on a dedicated server (not a VPS) in Germany with 1gbit/1gbit switch (200mbps guaranteed but in practice could 99% of the time get 80MB/s + ). Averaged around 3-5% DOA for me and about 2-4% orphans.

When I initially tried to set up my home connection, I was getting around 0-1% DOA and 15-20% orphans. A few percentage of the orphan rate was from being in the US instead of France/Germany/Netherlands where most of these dedicated servers & VPS are running. Most was from my 768kbps upstream cap.

Later on I was able to set it up w/ 0-1% DOA and an orphan rate under 10% (though it still wasn't as good as just using German remote server, after share time got changed to 30s)... anyway, the deal is, just have bitcoind connect to 1 or 2 servers & also your p2pool node need only connect to a handful of servers... you just have to pick the right ones. I have no clue what those are anymore. (ie, change outgoing connections to 0 and handpick the servers to connect to)

ed: i think you can find a VPS for a couple of bucks to run a bitcoind relay on

That's a decent idea about running a VPS for a bitcoind relay. I could stick p2pool on there too while I'm at it.

It still doesn't solve the high share difficulty problem though.

M

bitpop

legendary

Activity: 2912

Merit: 1060

Quote from: smoothrunnings on January 19, 2014, 07:13:40 PM

Quote from: bitpop on January 19, 2014, 06:57:11 PM

Quote from: smoothrunnings on January 19, 2014, 06:46:51 PM

Quote from: bkminer on January 19, 2014, 06:38:04 PM

Quote from: ikolubr on January 19, 2014, 06:33:37 PM

Quote from: forrestv on January 19, 2014, 05:53:12 PM

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Do I need to restart the p2pool or just a git pull should work?

Thank you.

go into p2pool directory and do a git pull then restart

Finally someone with a brain who spelled it out, what to do! LOL

Thanks for your help!

Wait so you know how to do that but my mention of running last commit didn't trigger this?

Obviously you haven't been paying attention in the other thread on setting up P2Pool? I have only had my pool setup for uhm, close to 24 hours now. With the questions I was asking its obvious I didn't know much about linux otherwise I would have been done ages ago. Thanks to the guys over at the openSUSE forum who did a great job at translating the ubuntu mumbo jumbo stuff into openSUSE.

It would have been more simpler if you had said.. run git pull on p2pool instead of saying it the other way. LOL

There is no need to complicate your life and the life of others.

Thanks,

Sorry that's cuz I don't know how to do it that far

zvs

legendary

Activity: 1680

Merit: 1000

https://web.archive.org/web/*/nogleg.com

Quote from: mdude77 on January 17, 2014, 10:03:43 PM

Quote from: iongchun on January 17, 2014, 09:42:34 PM

Quote from: mdude77 on January 17, 2014, 09:20:54 PM

You're comparing with others in p2pool. I'm comparing with non p2pool.

M

You could think in p2pool way.
If your good share rate is higher/lower than others in p2pool,
your average income is higher/lower than others in non-p2pool.
Then take low miner fee, tx fee, p2p, and coinbase tx as pros, and higher variance as cons.

Also, unless things have changed, p2pool can not be reliably run on a home DSL connection. That means folks like myself have to use a public node or suffer higher than normal rejects (and normal is high enough thank you!). That means you have two choices: trust the op of that public node, or get higher rejects. Both negate two supposed benefits of p2pool.

M

The pool I ran for bitcoins averaged ~110-115% efficiency, but that was on a dedicated server (not a VPS) in Germany with 1gbit/1gbit switch (200mbps guaranteed but in practice could 99% of the time get 80MB/s + ). Averaged around 3-5% DOA for me and about 2-4% orphans.

When I initially tried to set up my home connection, I was getting around 0-1% DOA and 15-20% orphans. A few percentage of the orphan rate was from being in the US instead of France/Germany/Netherlands where most of these dedicated servers & VPS are running. Most was from my 768kbps upstream cap.

Later on I was able to set it up w/ 0-1% DOA and an orphan rate under 10% (though it still wasn't as good as just using German remote server, after share time got changed to 30s)... anyway, the deal is, just have bitcoind connect to 1 or 2 servers & also your p2pool node need only connect to a handful of servers... you just have to pick the right ones. I have no clue what those are anymore. (ie, change outgoing connections to 0 and handpick the servers to connect to)

ed: i think you can find a VPS for a couple of bucks to run a bitcoind relay on

ikolubr

newbie

Activity: 18

Merit: 0

Here is working fine so far! Cheesy

oldbushie

member

Activity: 94

Merit: 10

Yeah I had another drop 2 hours after I pulled from git.

smoothrunnings

hero member

Activity: 630

Merit: 501

Quote from: forrestv on January 19, 2014, 05:02:16 PM

There is currently a problem and a fix is being worked on. For now, refusing incoming connections (--max-conns 0) is a temporary solution. Expect more news in the next half hour.

Just had it happen to me after applying the fix a couple of hours ago. I have added --max-conns 0 to my startup until a more perminate fix is found.

Thanks,

smoothrunnings

hero member

Activity: 630

Merit: 501

Quote from: bkminer on January 19, 2014, 07:59:26 PM

Quote from: smoothrunnings on January 19, 2014, 07:16:34 PM

It's working for me so far Rick, knock on wood.

You could always block or turn off port 9333 as a temporary measure and enable it later.

I should look at the code but I thought it would block the peer that sends bad shares before it went into it's loop that kills everything. I have a monit script setup to restart it when it starts to act up. Unfortunately Apple AirPorts cut the connection for a minute or so when changing that level of settings. I could just add an iptables rule..

Sounds like something I should find for openSUSE; the script that restarts it when something acts up.

bkminer

full member

Activity: 216

Merit: 100

Don't let the nam-shub in your operating system.

Quote from: smoothrunnings on January 19, 2014, 07:16:34 PM

It's working for me so far Rick, knock on wood.

You could always block or turn off port 9333 as a temporary measure and enable it later.

I should look at the code but I thought it would block the peer that sends bad shares before it went into it's loop that kills everything. I have a monit script setup to restart it when it starts to act up. Unfortunately Apple AirPorts cut the connection for a minute or so when changing that level of settings. I could just add an iptables rule..

smoothrunnings

hero member

Activity: 630

Merit: 501

Quote from: bkminer on January 19, 2014, 07:05:07 PM

Quote from: forrestv on January 19, 2014, 05:53:12 PM

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Latest commit did not seem to help... happened again right after first incoming peer connected.

-Rick

It's working for me so far Rick, knock on wood.

You could always block or turn off port 9333 as a temporary measure and enable it later.

smoothrunnings

hero member

Activity: 630

Merit: 501

Quote from: bitpop on January 19, 2014, 06:57:11 PM

Quote from: smoothrunnings on January 19, 2014, 06:46:51 PM

Quote from: bkminer on January 19, 2014, 06:38:04 PM

Quote from: ikolubr on January 19, 2014, 06:33:37 PM

Quote from: forrestv on January 19, 2014, 05:53:12 PM

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Do I need to restart the p2pool or just a git pull should work?

Thank you.

go into p2pool directory and do a git pull then restart

Finally someone with a brain who spelled it out, what to do! LOL

Thanks for your help!

Wait so you know how to do that but my mention of running last commit didn't trigger this?

Obviously you haven't been paying attention in the other thread on setting up P2Pool? I have only had my pool setup for uhm, close to 24 hours now. With the questions I was asking its obvious I didn't know much about linux otherwise I would have been done ages ago. Thanks to the guys over at the openSUSE forum who did a great job at translating the ubuntu mumbo jumbo stuff into openSUSE.

It would have been more simpler if you had said.. run git pull on p2pool instead of saying it the other way. LOL

There is no need to complicate your life and the life of others.

Thanks,

bitpop

legendary

Activity: 2912

Merit: 1060

Quote from: bkminer on January 19, 2014, 07:05:07 PM

Quote from: forrestv on January 19, 2014, 05:53:12 PM

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Latest commit did not seem to help... happened again right after first incoming peer connected.

-Rick

Give it time to block them

bkminer

full member

Activity: 216

Merit: 100

Don't let the nam-shub in your operating system.

Quote from: forrestv on January 19, 2014, 05:53:12 PM

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Latest commit did not seem to help... happened again right after first incoming peer connected.

-Rick

bitpop

legendary

Activity: 2912

Merit: 1060

Quote from: smoothrunnings on January 19, 2014, 06:46:51 PM

Quote from: bkminer on January 19, 2014, 06:38:04 PM

Quote from: ikolubr on January 19, 2014, 06:33:37 PM

Quote from: forrestv on January 19, 2014, 05:53:12 PM

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Do I need to restart the p2pool or just a git pull should work?

Thank you.

go into p2pool directory and do a git pull then restart

Finally someone with a brain who spelled it out, what to do! LOL

Thanks for your help!

Wait so you know how to do that but my mention of running last commit didn't trigger this?

smoothrunnings

hero member

Activity: 630

Merit: 501

Quote from: bkminer on January 19, 2014, 06:38:04 PM

Quote from: ikolubr on January 19, 2014, 06:33:37 PM

Quote from: forrestv on January 19, 2014, 05:53:12 PM

Try the most recent commit (012a8830), if you can. It bans peers that send invalid shares (for an hour), so it should help.

Do I need to restart the p2pool or just a git pull should work?

Thank you.

go into p2pool directory and do a git pull then restart

Finally someone with a brain who spelled it out, what to do! LOL

Thanks for your help!

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