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

[PatMan]

Right, thanks rav3n, but 9333 is already open. Is there a reason why the defaults are 40 & 6? And would there be any benefit in changing them?

Still a noob, still learning......

The more nodes you connect to the faster your shares reach the entire network and the fewer stales you will have. But if you are on a home internet connection you don't want to saturate your upload bandwidth because that will just mess everything up and Bitcoin needs to take a chunk of bandwidth too. So try to strike a balance that suits your connection.

cabin,

Right, thanks rav3n, but 9333 is already open. Is there a reason why the defaults are 40 & 6? And would there be any benefit in changing them?

Still a noob, still learning......

The more nodes you connect to the faster your shares reach the entire network and the fewer stales you will have. But if you are on a home internet connection you don't want to saturate your upload bandwidth because that will just mess everything up and Bitcoin needs to take a chunk of bandwidth too. So try to strike a balance that suits your connection.

Thanks cabin,

Seeing as my internet is snails pace anyway I'll leave those settings at default then.....

[Aseras]

so we hit the halving. and p2pool thinks the next block is worth 38.55495555 BTC

there's not a chance in hell there's 13.5btc in transaction fees.

[eleuthria]

so we hit the halving. and p2pool thinks the next block is worth 38.55495555 BTC

there's not a chance in hell there's 13.5btc in transaction fees.

There is.  Looks like some people are celebrating by paying big txfees for the first 25 BTC block.

[Aseras]

so we hit the halving. and p2pool thinks the next block is worth 38.55495555 BTC

there's not a chance in hell there's 13.5btc in transaction fees.

There is.  Looks like some people are celebrating by paying big txfees for the first 25 BTC block.

yep guess so,

http://blockchain.info/block-index/322335/000000000000048b95347e83192f69cf0366076336c639f9b7228e9ba171342e

lol

[twmz]

That's looking better, even though it is early doors. How did you manage to get connected to so many peers (30 &24 in)? I've never managed to get above 11 & 0 in.....

That's 6 outgoing (which is the recently revised default) and those always fill up quickly.  The incoming ones always take a few hours to re-arrive after I restart p2pool.  The only way another node will connect to me is if it is restarted, itself (and therefore needs to re-establish it's 6 outgoing connections) or if it loses one of its 6 outgoing connections.  Also, nodes prefer to connect to "old" peers that have been around for a long time, and my node has been running consistently for about a year, so I don't usually have to wait more than a day to be full on incoming connections again.

[K1773R]

That's looking better, even though it is early doors. How did you manage to get connected to so many peers (30 &24 in)? I've never managed to get above 11 & 0 in.....

That's 6 outgoing (which is the recently revised default) and those always fill up quickly.  The incoming ones always take a few hours to re-arrive after I restart p2pool.  The only way another node will connect to me is if it is restarted, itself (and therefore needs to re-establish it's 6 outgoing connections) or if it loses one of its 6 outgoing connections.  Also, nodes prefer to connect to "old" peers that have been around for a long time, and my node has been running consistently for about a year, so I don't usually have to wait more than a day to be full on incoming connections again.

i changed the code to create 30 outgoing connections, its fairly easy!

[forrestv]

That's looking better, even though it is early doors. How did you manage to get connected to so many peers (30 &24 in)? I've never managed to get above 11 & 0 in.....

That's 6 outgoing (which is the recently revised default) and those always fill up quickly.  The incoming ones always take a few hours to re-arrive after I restart p2pool.  The only way another node will connect to me is if it is restarted, itself (and therefore needs to re-establish it's 6 outgoing connections) or if it loses one of its 6 outgoing connections.  Also, nodes prefer to connect to "old" peers that have been around for a long time, and my node has been running consistently for about a year, so I don't usually have to wait more than a day to be full on incoming connections again.

i changed the code to create 30 outgoing connections, its fairly easy!

There is a reason it has a low default and is limited to 10: Outgoing connections are a limited resource, since few nodes are set up to accept incoming connections. See the discussion of the "Hub" patch to Bitcoin.

Besides that, you don't need that many connections. Bandwidth usage scales linearly with number of connections, but the benefit of increased connections on your orphan rate is small.

[K1773R]

That's looking better, even though it is early doors. How did you manage to get connected to so many peers (30 &24 in)? I've never managed to get above 11 & 0 in.....

That's 6 outgoing (which is the recently revised default) and those always fill up quickly.  The incoming ones always take a few hours to re-arrive after I restart p2pool.  The only way another node will connect to me is if it is restarted, itself (and therefore needs to re-establish it's 6 outgoing connections) or if it loses one of its 6 outgoing connections.  Also, nodes prefer to connect to "old" peers that have been around for a long time, and my node has been running consistently for about a year, so I don't usually have to wait more than a day to be full on incoming connections again.

i changed the code to create 30 outgoing connections, its fairly easy!

There is a reason it has a low default and is limited to 10: Outgoing connections are a limited resource, since few nodes are set up to accept incoming connections. See the discussion of the "Hub" patch to Bitcoin.

Besides that, you don't need that many connections. Bandwidth usage scales linearly with number of connections, but the benefit of increased connections on your orphan rate is small.

traffic and latency arent my problem so i can shrink it up gonna try 100 later just for fun ^^

[lenny_]

so we hit the halving. and p2pool thinks the next block is worth 38.55495555 BTC

there's not a chance in hell there's 13.5btc in transaction fees.

Actually there is  Look: https://blockchain.info/block-height/210000
Transaction Fees    13.56295554 BTC
It was planned action (by Twitters), for 210000 block to be remembered in history

[mdude77]

Well.. after about 24 hours, the new version isn't helping me any.  I still get 5-10% rejects from cgminer, and 25% stale/dead from p2pool.  Maybe stratum will help.

M

[lumberjack]

After a git pull I'm seeing this line repeated very often in the log.


2012-11-29 00:00:01.675185 Punishing share for 'not all txs present'! Jumping from fdbd8fa8 to b29d41a0!
2012-11-29 00:00:01.835841 Punishing share for 'not all txs present'! Jumping from fdbd8fa8 to b29d41a0!
2012-11-29 00:00:01.887518 Punishing share for 'not all txs present'! Jumping from fdbd8fa8 to b29d41a0!
2012-11-29 00:00:01.940477 Punishing share for 'not all txs present'! Jumping from fdbd8fa8 to b29d41a0!

[rav3n_pl]

Latest git 9.1-9-gb246991 works much better for me.
Memory usage on linux finally drop to around 500MB, no doas.
Windows binary (32 bit) on my skydrive.

[PatMan]

OK, after 18 hours uptime I can't see any significant change - still at 25%+ orphan/dead rate with large memory usage. I have also noticed a lot of the "tx" comments in the logs, as well as the "punishing share for stale" thing - whats with that? Even with the high stale rate I notice we're still getting payouts on blocks (albeit lower since halving) so it's not all bad, although I find myself wondering what the payouts would be with a normal reject/orphaned/dead rate......

Right, just switched over to the newest git from Rav3n's skydrive - thanks for the heads up Rav3n. Lets see how this baby goes......

[mdude77]

Latest git 9.1-9-gb246991 works much better for me.
Memory usage on linux finally drop to around 500MB, no doas.
Windows binary (32 bit) on my skydrive.

Is there a way to see the git version when you download as zip?  once upon a time it was in the filenname, now everything is "p2pool-master".

M

[spiccioli]

Latest git 9.1-9-gb246991 works much better for me.
Memory usage on linux finally drop to around 500MB, no doas.
Windows binary (32 bit) on my skydrive.

Is there a way to see the git version when you download as zip?  once upon a time it was in the filenname, now everything is "p2pool-master".

M

mdude,

the best way is to issue a git clone the first time and then, cd into p2pool directory and issue a git pull when you need a new version.

you have to install git, but from then on it will update itself seamlessly.

spiccioli

[rav3n_pl]

He meant windows.
I not see how it ca be done automagically.
I`m doing it by gitpulling on linux, see version number then compiling windows version using that data.

[spiccioli]

He meant windows.
I not see how it ca be done automagically.
I`m doing it by gitpulling on linux, see version number then compiling windows version using that data.

rav3n_pl,

sorry, I'm using linux only on my rigs.

You can run python and git on windows, though, so it should work (at least in theory).

spiccioli.

[PatMan]

OK, after 18 hours uptime I can't see any significant change - still at 25%+ orphan/dead rate with large memory usage. I have also noticed a lot of the "tx" comments in the logs, as well as the "punishing share for stale" thing - whats with that? Even with the high stale rate I notice we're still getting payouts on blocks (albeit lower since halving) so it's not all bad, although I find myself wondering what the payouts would be with a normal reject/orphaned/dead rate......

Right, just switched over to the newest git from Rav3n's skydrive - thanks for the heads up Rav3n. Lets see how this baby goes......

Well, after only being up for a few hours with this latest release I can already see a 200% improvement - 10 shares - 0 stales - 0 dead. Now THATS more like it, back to normal again, so far. What ever changes were implemented in this version seem to have worked wonders for my set up at least. Noticed some more additions to the logs that I've not seen before:

KNOWN: 141425
MINING: 60749

It's showing often, can someone explain these? I presume it's some kind of checking that has helped eliminate the bad shares?

[Aseras]

I am only seeing 6 peers in 9.1 vs 10-15 on 9.0

[rav3n_pl]

You can run python and git on windows, though, so it should work (at least in theory).

Just installed git for windowz ;]

Code:

C:\msysgit\git\p2pool>run_p2pool.py --version
b016b6b

Sadly it is not showing full version, only git hash :/
Same after compilation to exe.
Looks like "manual" way is only way for dat windowz to show full version number.