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

[norgan]

Is it just me or did the p2pool hash rate just double to almost 1ph/s?!

I'm showing 682TH/s on my node, a nice jump....

If you have some new miners hitting your node you may want to set your share diff and pseudo share diff on your miner....

Code:

bitcoin_address/<share>+<pseudo_share>

If your running S1's set <share> to 0 ("0" defaults to lowest p2pool diff, currently 1677854.73)

And <pseudo_share> to 220.4 (optimized for 190GH/s)

<pseudo_share> is calculated as your hash rate in KH/s times 0.00000116

i.e. 190,000,000 * 0.00000116 = 220.4

Here is an example for an ant S1:

Code:

19vXrwKGUhK4cCU8tA4kWZgbChcmh9a6qj/0+220.4

If you have a hash rate over 1TH/s you might consider upping your share diff to something higher then the p2pool minimum to reduce network traffic and increase the value of your shares...

Thanks for the info.

[1714204457]

1714204457

[1714204457]

1714204457

[1714204457]

1714204457

[1714204457]

1714204457

[1714204457]

1714204457

[1714204457]

1714204457

[forrestv]

Any word on when the stats page http://p2pool.info/ is coming back?  It's been down for days now.  It was fully transfered to forrestv a few months ago right?

Yes, I control it, and I'll fix it soon, hopefully in the next day.

[mdude77]

Anyone have any definitive thoughts on how to get S2s working with p2pool at full capacity?  I can't justify losing 10% of my hashpower to use p2pool.

M

[PatMan]

Anyone have any definitive thoughts on how to get S2s working with p2pool at full capacity?  I can't justify losing 10% of my hashpower to use p2pool.

M

I got one arriving tomorrow - I'll let you know how I get on, but 10% is too much to lose for sure - especially at the price of them 

[mdude77]

Anyone have any definitive thoughts on how to get S2s working with p2pool at full capacity?  I can't justify losing 10% of my hashpower to use p2pool.

M

I got one arriving tomorrow - I'll let you know how I get on, but 10% is too much to lose for sure - especially at the price of them 

I've got two S2s.  Both behave the same way.  Within minutes of pointing at a p2pool node, the hash rate drops to about 930gh/s or less.

M

[windpath]

Anyone have any definitive thoughts on how to get S2s working with p2pool at full capacity?  I can't justify losing 10% of my hashpower to use p2pool.

M

I got one arriving tomorrow - I'll let you know how I get on, but 10% is too much to lose for sure - especially at the price of them 

I've got two S2s.  Both behave the same way.  Within minutes of pointing at a p2pool node, the hash rate drops to about 930gh/s or less.

M

Hey mdude...

I know you pretty knowledgeable, but figured I'd give you my run through:

1. I'm not sure if your node is local to your miners, whats your latency?
2. Set your pseudo share difficulty
3. give it some time? looking at your graphs I don't see a consecutive length of time of ~1TH/s hashing, and I do see good effiency and a decent share count, it will take some time to accurately represent your estimated payout, 3-4 days of consistent mining to get some shares in and see where your at...

Other than that, I peeked at the graphs on your node and everything else seems within regular parameters...

[mdude77]

Anyone have any definitive thoughts on how to get S2s working with p2pool at full capacity?  I can't justify losing 10% of my hashpower to use p2pool.

M

I got one arriving tomorrow - I'll let you know how I get on, but 10% is too much to lose for sure - especially at the price of them 

I've got two S2s.  Both behave the same way.  Within minutes of pointing at a p2pool node, the hash rate drops to about 930gh/s or less.

M

Hey mdude...

I know you pretty knowledgeable, but figured I'd give you my run through:

1. I'm not sure if your node is local to your miners, whats your latency?
2. Set your pseudo share difficulty
3. give it some time? looking at your graphs I don't see a consecutive length of time of ~1TH/s hashing, and I do see good effiency and a decent share count, it will take some time to accurately represent your estimated payout, 3-4 days of consistent mining to get some shares in and see where your at...

Other than that, I peeked at the graphs on your node and everything else seems within regular parameters...

1 - I've observed this running locally, across the country (my public node), and at least one other node that's close by.
2 - I've tried setting pseudo share difficulty as high as possible, which is apparently 1k.
3 - I stopped running at p2pool a while ago because of this problem.  Before that I tried different things over a period of close to a week before I gave up.

M

[windpath]

Anyone have any definitive thoughts on how to get S2s working with p2pool at full capacity?  I can't justify losing 10% of my hashpower to use p2pool.

M

I got one arriving tomorrow - I'll let you know how I get on, but 10% is too much to lose for sure - especially at the price of them 

I've got two S2s.  Both behave the same way.  Within minutes of pointing at a p2pool node, the hash rate drops to about 930gh/s or less.

M

Hey mdude...

I know you pretty knowledgeable, but figured I'd give you my run through:

1. I'm not sure if your node is local to your miners, whats your latency?
2. Set your pseudo share difficulty
3. give it some time? looking at your graphs I don't see a consecutive length of time of ~1TH/s hashing, and I do see good effiency and a decent share count, it will take some time to accurately represent your estimated payout, 3-4 days of consistent mining to get some shares in and see where your at...

Other than that, I peeked at the graphs on your node and everything else seems within regular parameters...

1 - I've observed this running locally, across the country (my public node), and at least one other node that's close by.
2 - I've tried setting pseudo share difficulty as high as possible, which is apparently 1k.
3 - I stopped running at p2pool a while ago because of this problem.  Before that I tried different things over a period of close to a week before I gave up.

M

It's strange... maybe our friends at Bitmain played with the CGMiner code some more and created an unintentional glitch?

All my S1's report accurately, don't have an S2 to play with...

[jonnybravo0311]

It would be nice to hear from others with S2s on p2pool to find out if the same loss of hash rate occurs for them as well.  Unfortunately, I don't have one to test, either.  I will, however, have an SP-10 delivered tomorrow - which unfortunately won't be hashing until Saturday evening because I'm on the other freaking side of the planet.  I will definitely be trying it out on p2pool, Eligius, BTCGuild and GHash.io to see if there are any significant differences in hash rate.

Anyone with S2s running on p2pool?

[-ck]

Kano has an S2 now and is working on official code for cgminer that hopefully will rectify the behaviour of the driver they included with it.

[-ck]

Is it just me or did the p2pool hash rate just double to almost 1ph/s?!

Last time it did a big jump like that it was the attack that was redirecting people's hashes from other pools to their own p2pool node.

[jonnybravo0311]

Kano has an S2 now and is working on official code for cgminer that hopefully will rectify the behaviour of the driver they included with it.

Good news for S2 owners.

[ceslick]

Hi,

Tried this, didn't work

Managed to get it working by reinstalling twisted and zope a few times... Also forced python version to 2.7

Lets see how it goes

Will test a while

I did notice one error at one stage where it said it lost connection to bitcoind for 1.5 minutes. Any ideas?

Tried purging those and re installing them

Same result...

Twisted version 13.0.0-1 is installed

cd to folder where you have p2pool

cd /p2pool

./configure

make -j12

should do it

Replace ubuntu with Gentoo

[PatMan]

Kano has an S2 now and is working on official code for cgminer that hopefully will rectify the behaviour of the driver they included with it.

This is good news! Kano done a great job with the S1 miner tweaks - I use it on all my S1's with excellent results.

I will gladly donate to the development of an S2 equivalent - suggest everyone else do the same 

Peace.

[norgan]

Kano has an S2 now and is working on official code for cgminer that hopefully will rectify the behaviour of the driver they included with it.

This is good news! Kano done a great job with the S1 miner tweaks - I use it on all my S1's with excellent results.

I will gladly donate to the development of an S2 equivalent - suggest everyone else do the same 

Peace.

whats the S1 miner tweaks he has done?

[jedimstr]

Kano has an S2 now and is working on official code for cgminer that hopefully will rectify the behaviour of the driver they included with it.

This is good news! Kano done a great job with the S1 miner tweaks - I use it on all my S1's with excellent results.

I will gladly donate to the development of an S2 equivalent - suggest everyone else do the same 

Peace.

whats the S1 miner tweaks he has done?

Replacement updated version of CGMiner for the S1:
https://github.com/kanoi/cgminer-binaries/tree/master/AntS1

[norgan]

Kano has an S2 now and is working on official code for cgminer that hopefully will rectify the behaviour of the driver they included with it.

This is good news! Kano done a great job with the S1 miner tweaks - I use it on all my S1's with excellent results.

I will gladly donate to the development of an S2 equivalent - suggest everyone else do the same 

Peace.

whats the S1 miner tweaks he has done?

Replacement updated version of CGMiner for the S1:
https://github.com/kanoi/cgminer-binaries/tree/master/AntS1

awesome thanks!

[gigabitfx]

Hi Windpath, thanks for the info here, im running some s1 and was having hard time with google on a definitive response to setting the pseudo share.

couple of questions
1. is 0.00000116 a static constant, or based off dynamic number?  Wondering if i need to redo the math periodically to keep my miners running efficiently.
2. do you know of any downsides to restarting p2pool, i noticed i lost a few shares once i had done so, but technically i dont understand why that would be.  i did however update the -a payout address, perhaps that restages the pool?
3. "expected time to share" seems to stay around 7-12hrs, im assuming its because the pool doesn't have any stats to work off of yet?
4. "payout if a block were found NOW" seems to remain at 0, any tips on that?
5. know of any p2pool advanced docs/manuals out there?

Thanks for any info

Is it just me or did the p2pool hash rate just double to almost 1ph/s?!

I'm showing 682TH/s on my node, a nice jump....

If you have some new miners hitting your node you may want to set your share diff and pseudo share diff on your miner....

Code:

bitcoin_address/<share>+<pseudo_share>

If your running S1's set <share> to 0 ("0" defaults to lowest p2pool diff, currently 1677854.73)

And <pseudo_share> to 220.4 (optimized for 190GH/s)

<pseudo_share> is calculated as your hash rate in KH/s times 0.00000116

i.e. 190,000,000 * 0.00000116 = 220.4

Here is an example for an ant S1:

Code:

19vXrwKGUhK4cCU8tA4kWZgbChcmh9a6qj/0+220.4

If you have a hash rate over 1TH/s you might consider upping your share diff to something higher then the p2pool minimum to reduce network traffic and increase the value of your shares...
[/quote]

[windpath]

Hi Windpath, thanks for the info here, im running some s1 and was having hard time with google on a definitive response to setting the pseudo share.

couple of questions
1. is 0.00000116 a static constant, or based off dynamic number?  Wondering if i need to redo the math periodically to keep my miners running efficiently.
2. do you know of any downsides to restarting p2pool, i noticed i lost a few shares once i had done so, but technically i dont understand why that would be.  i did however update the -a payout address, perhaps that restages the pool?
3. "expected time to share" seems to stay around 7-12hrs, im assuming its because the pool doesn't have any stats to work off of yet?
4. "payout if a block were found NOW" seems to remain at 0, any tips on that?
5. know of any p2pool advanced docs/manuals out there?

Thanks for any info

Hi Gigabit,

I'm by no means the expert, still studying the code and learning, but I'll give you my best advice and if I'm wrong, or there is a better solution hopefully someone will jump in...

1. It's constant.
2. Restarting will dump all your peers, and re-start many of the stats. Accepted shares will not be lost during a restart, but will not show on your stats page after, obviously shares submitted during a restart will be lost or stale by the time your node is back up. I try to limit restarts as much as possible.
3. Expected time to share is based on your ~estimated~ hash rate, is subject to your miners luck/variance, and can vary greatly.
4. Once you get some shares in the current block this will change, also subject to variance, some days will be higher and some lower.
5. I don't. There are some good tutorials for getting it up and running efficiently here on the forum, and on some alt-coin forums, but no definitive docs that I have found...

Here is an example of the variance/luck, the bottom 2 miners have both been consistently mining on p2pool, the bottom one is currently in a streak of good luck, while the middle one is in a streak of what I'd call less then ideal luck...



It all balances out over time, a key to successfully mining on p2pool is having the patience and consistency to stick with it until it does

[mdude77]

Hi Windpath, thanks for the info here, im running some s1 and was having hard time with google on a definitive response to setting the pseudo share.

In case you missed it, make sure you update your S1 with the cgminer patch for p2pool.

https://github.com/kanoi/cgminer-binaries/tree/master/AntS1

M