Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 350. (Read 2591964 times)
Wow!!! 2 blocks in 1 day!!! I'll take that anyday!!
@ PatMan - emailed you some info dude 
Got it my man - good stuff
EDIT: Everything has been sent to Bitmain - hope to get some news soon......fingers crossed
Thanks again everyone for your input.
@ PatMan - emailed you some info dude
So by default p2pool set diff for the entire node's hashrate and that made my slower miners choke on big diff.
Higher diff is in no way harmful to slow miners, and if anything is advantageous by limiting wasted share processing (which does not contribute to your income). It's a common misconception that high diff is bad for slow miners - it only increases the variance on those miners on regular pools and on p2pool all shares are pseudoshares unless they're very high diff shares so they have absolutely zero influence on neither your payout nor your variance.Thanks Con
************URGENT**********
@forrestv - This is your chance to prove to p2pool users that you actually care - I & every user here would like to see some input from you regarding this - please provide any info you can.....
@forrestv - This is your chance to prove to p2pool users that you actually care - I & every user here would like to see some input from you regarding this - please provide any info you can.....
BIG +1, S2's and upcoming S3's are ciritical to our success.
I'd like to start a bounty for forrestv to complete this.
I will start it with a BTC0.50 bounty offered to forrestv for a working solution for p2pool/anitminer S2 & S3 compatibility with the Ants achieving expected hashrate and shares.
Anyone is welcome to contribute to the donation address, bounty is paid to forrestv (or his designee) upon a working, distributed solution or returned in full in 30 days, I will pay return tx fees for any donation over BTC0.001, if your donation is less, consider it donated.
Bounty Address: 1Ft1DZ4EcpH1jFttDoPwsFbe11a6diyZ1H
https://blockchain.info/address/1Ft1DZ4EcpH1jFttDoPwsFbe11a6diyZ1H
Signed message:
Code:
forrestv p2pool antminer s2 and s3 compatibility fix.
Message signature:
Code:
G7zuvJ7/LPv7LpZveAsQWet1gAR42bnwFRVPB7NsnGqPnWkN8bqSSN1UwR+NnfDs/8LkruqZcVsTTdfcy5pcNj4=
Please contribute.
Edit: Any additional donations (over BTC0.001) will be returned to donation address or paid to Forrest or his designee on or before July 25th, 2014.
My hope is to pay Forrest for work done, lets make the bounty worthwhile.
Donated
7f9e8ad8756685ef911f3cbb2a0c4ae74b3851dbfa0f1b312154fdf689ee6b11
Confirmed BTC0.25
Total bounty currently BTC0.75
Interesting, thanks for that. I've removed it from my S1 and it seems to hash a little bit higher now and can see the diff adjusting. will let that run for a it and see how it looks.
Just when you think you are starting to understand it all, something pops up and you re-evaluate your tactic lol
Just when you think you are starting to understand it all, something pops up and you re-evaluate your tactic lol
Does that mean you'll be updating your tips page at your pool?
http://www.norgzpool.net.au/antminer.html
The settings you suggests there seem to have been working fine on my miners ( /0+220.4 for my S1's and similar calculations for other rigs). Gonna be a pain to change them all back to default in all of my config scripts.
My problem has been that I had a lot of miners and the default diff went really high without specific setting per miner... So by default p2pool set diff for the entire node's hashrate and that made my slower miners choke on big diff.
My worry was that I have a miner in my node 3 times faster than mine and I also have a smaller miner that I use. Always looking for options to optimize those. So far the differences have been pretty small.
I tought there was a bug in p2pool, had my username/3000000 , when i took the 3000000 of it didnt go down to 1200000 that webpage was showing - even node reboot didnt calm it down. It stayed at ~1600000 even with 2 erupters 670mh
Had to put username/1000000 and then it started to follow..
Had to put username/1000000 and then it started to follow..
Interesting, thanks for that. I've removed it from my S1 and it seems to hash a little bit higher now and can see the diff adjusting. will let that run for a it and see how it looks.
Just when you think you are starting to understand it all, something pops up and you re-evaluate your tactic lol
Just when you think you are starting to understand it all, something pops up and you re-evaluate your tactic lol
Does that mean you'll be updating your tips page at your pool?
http://www.norgzpool.net.au/antminer.html
The settings you suggests there seem to have been working fine on my miners ( /0+220.4 for my S1's and similar calculations for other rigs). Gonna be a pain to change them all back to default in all of my config scripts.
My problem has been that I had a lot of miners and the default diff went really high without specific setting per miner... So by default p2pool set diff for the entire node's hashrate and that made my slower miners choke on big diff.
My worry was that I have a miner in my node 3 times faster than mine and I also have a smaller miner that I use. Always looking for options to optimize those. So far the differences have been pretty small.
So by default p2pool set diff for the entire node's hashrate and that made my slower miners choke on big diff.
Higher diff is in no way harmful to slow miners, and if anything is advantageous by limiting wasted share processing (which does not contribute to your income). It's a common misconception that high diff is bad for slow miners - it only increases the variance on those miners on regular pools and on p2pool all shares are pseudoshares unless they're very high diff shares so they have absolutely zero influence on neither your payout nor your variance. Interesting, thanks for that. I've removed it from my S1 and it seems to hash a little bit higher now and can see the diff adjusting. will let that run for a it and see how it looks.
Just when you think you are starting to understand it all, something pops up and you re-evaluate your tactic lol
Just when you think you are starting to understand it all, something pops up and you re-evaluate your tactic lol
Does that mean you'll be updating your tips page at your pool?
http://www.norgzpool.net.au/antminer.html
The settings you suggests there seem to have been working fine on my miners ( /0+220.4 for my S1's and similar calculations for other rigs). Gonna be a pain to change them all back to default in all of my config scripts.
My problem has been that I had a lot of miners and the default diff went really high without specific setting per miner... So by default p2pool set diff for the entire node's hashrate and that made my slower miners choke on big diff.
Hey guys,
Thanks to everyone for the info regarding the S2 (S3) p2pool issues. I have just rebuilt my node & am syncing the wallets now - as soon as it's ready I will take the screens requested by Bitmain & send everything off to them. Thanks & kudos to Kano for getting back to me also, his work on the S1 & S2's is massive.
There are still a couple of hours worth of syncing to be done, so if anyone has anything else to add that they think might help, just post or PM me.
Lets hope we can get it sorted
Thanks to everyone for the info regarding the S2 (S3) p2pool issues. I have just rebuilt my node & am syncing the wallets now - as soon as it's ready I will take the screens requested by Bitmain & send everything off to them. Thanks & kudos to Kano for getting back to me also, his work on the S1 & S2's is massive.
There are still a couple of hours worth of syncing to be done, so if anyone has anything else to add that they think might help, just post or PM me.
Lets hope we can get it sorted
Nice one Patman.
I still find it ironic that we see pool rate drop and blocks fewer but we seem to be getting more traction on code development. I can't help but speculate what that means for p2pool.
Will petamine add their hashing to p2pool effectively pushing us all out due to diff rising or will a change come that no only avoids this but even perhaps takes advantage of it, as in more blocks for miners on p2pool. and the even stranger thing is the number of donations made to p2pool of late.
Funny times we are seeing right now.
Hey guys,
Thanks to everyone for the info regarding the S2 (S3) p2pool issues. I have just rebuilt my node & am syncing the wallets now - as soon as it's ready I will take the screens requested by Bitmain & send everything off to them. Thanks & kudos to Kano for getting back to me also, his work on the S1 & S2's is massive.
There are still a couple of hours worth of syncing to be done, so if anyone has anything else to add that they think might help, just post or PM me.
Lets hope we can get it sorted
Thanks to everyone for the info regarding the S2 (S3) p2pool issues. I have just rebuilt my node & am syncing the wallets now - as soon as it's ready I will take the screens requested by Bitmain & send everything off to them. Thanks & kudos to Kano for getting back to me also, his work on the S1 & S2's is massive.
There are still a couple of hours worth of syncing to be done, so if anyone has anything else to add that they think might help, just post or PM me.
Lets hope we can get it sorted
Interesting, thanks for that. I've removed it from my S1 and it seems to hash a little bit higher now and can see the diff adjusting. will let that run for a it and see how it looks.
Just when you think you are starting to understand it all, something pops up and you re-evaluate your tactic lol
Just when you think you are starting to understand it all, something pops up and you re-evaluate your tactic lol
You could always manually adjust the share difficulty to get lower variances afaik.
you mean lower the diff?MYBTCADDRESS/1+1
But all that will do is flood the node with difficulty 1 shares from your miner.
my understanding is it ensures your lower hash rate doesn't get lost in the higher hash rate of other miners on your node. If you are the only one on your node it shouldn't matter.
btw a bock! yay!
As for the difficulty, I'm not really sure how setting it would have any effect on low hash rate miners. Your miner must find a share that satisfies the difficulty requirements of the share chain, regardless of whether or not you have 1GH/s or 1TH/s. Currently, that is about 1.2M. Setting your pseudo difficulty (by using the +xxx after your BTC address) doesn't have any effect on the actual share difficulty. All it does is make graphs look nicer. The lower you set it, the smoother the graph is - at the price of flooding the node with shares that have no chance of ever being accepted. By default, the node will dynamically adjust the pseudo-share difficulty to get 1 share per second:
Code:
target = min(target, bitcoin_data.average_attempts_to_target(local_hash_rate * 1))
I think setting the difficulty (using the /xxx after your BTC address) is really more for the miners with exceptionally high hash rates compared to others. I'm not sure anyone actually uses this. However, like with setting pseudo-difficulty, the node dynamically adjusts your difficulty to limit you to 1.67% of the pool's shares:
Code:
desired_share_target = min(desired_share_target, bitcoin_data.average_attempts_to_target(local_hash_rate * self.node.net.SHARE_PERIOD / 0.0167))
fwiw, a while back I also emailed bitmain about p2pool. I also asked that they work with Kano ... and give him the code to their S2 so he can figure things out. I got the same response, about forwarding info to their engineers.
The symptoms are as others described: they max out around 920-930gh/s upon startup, and slowly decline over time from there.
I agree with what others have said: all bitmain has to do is setup their own node and point an S2 to it to see what's going on.
M
The symptoms are as others described: they max out around 920-930gh/s upon startup, and slowly decline over time from there.
I agree with what others have said: all bitmain has to do is setup their own node and point an S2 to it to see what's going on.
M
You could always manually adjust the share difficulty to get lower variances afaik.
you mean lower the diff?MYBTCADDRESS/1+1
But all that will do is flood the node with difficulty 1 shares from your miner.
my understanding is it ensures your lower hash rate doesn't get lost in the higher hash rate of other miners on your node. If you are the only one on your node it shouldn't matter.
btw a bock! yay!
You could always manually adjust the share difficulty to get lower variances afaik.
you mean lower the diff?MYBTCADDRESS/1+1
But all that will do is flood the node with difficulty 1 shares from your miner.
You could always manually adjust the share difficulty to get lower variances afaik.
you mean lower the diff? 
You could always manually adjust the share difficulty to get lower variances afaik.
hmm my node hasn't picked up a share in over 5 hours. hashing at 700gh/s+ and usually a share comes up every couple of hours. anyone else seeing this?
That's just variance for you... my SP10 has gone for over 6 hours without finding a share. I've had my S1s go for 22 hours and more without finding shares. It happens.I've learned that those "Expected time to..." values are not worth looking at unless you want to get ulcers and stress headaches trying to tweak things into oblivion. As long as your node's efficiency rating/range has 100% in it, you're pretty much right on target.
Jump to: