Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 222. (Read 2592023 times)
February 06, 2015, 08:56:54 AM
long live p2pool
February 06, 2015, 07:35:49 AM
Good to see new users adopting p2pool & plenty of info being exchanged here lately, p2pool has a great community thing going on.
Thanks also to the donations from whoever you are - very generous!
Thanks also to the donations from whoever you are - very generous!
February 06, 2015, 05:05:59 AM
The Chicago node that I am using pings at 51ms. Can I expects do much better running my own node?
You'll always do better with your own node.
EDIT: assuming you have the bandwidth for it.
M
February 06, 2015, 05:05:33 AM
The Chicago node that I am using pings at 51ms. Can I expect to do much better running my own node?
February 06, 2015, 04:26:47 AM
Jonny answered back on my whale on the node question. Will it affect the other miners?
Here's his answer:
"Short answer is yes... That miner with 75TH/s is accounted for by the node and it ups the share difficulty. Now, if that miner knows what he's doing, he'll account for it himself by using /xxxx after his address ... Where xxx is a value greater than the typical share difficulty. Example if the share difficulty is 10000000 then that user would do something like ADDRESS/100000000."
Whale, if your watching, do me a favor, would you?
S
Fancy seeing you here. Seeing your post in the thread I realized you're on my node!Here's his answer:
"Short answer is yes... That miner with 75TH/s is accounted for by the node and it ups the share difficulty. Now, if that miner knows what he's doing, he'll account for it himself by using /xxxx after his address ... Where xxx is a value greater than the typical share difficulty. Example if the share difficulty is 10000000 then that user would do something like ADDRESS/100000000."
Whale, if your watching, do me a favor, would you?
S
That jump in hash rate is me... I rented some heavy firepower for a day for fun. It'll be done in about 4 hours or so. The reported rate you're seeing on windpath's node is because I haven't ramped up to the full shares I should have with 95TH/s. I would need to keep that level of hashing up for another few days for it to catch up.
As for your miner, it is hitting a bad luck streak. It is all part and parcel of the way p2pool works. I have an S3 on a node that didn't find a share for 5 days!
Hilarious. I'll be back.
February 06, 2015, 02:20:59 AM
Another block and more donations.
Thank you very much!
Thank you very much!
February 05, 2015, 09:51:46 PM
Don't think of it as competing with miners on the same node, you are completing (and collaborating) with the whole pool.
Also, node efficiency is a poor indicator on any node with more then 1 miner. A single miner with a high latency can bring node efficiency way down, while your miners may be mining very efficiently.
Look at your latency to the node, the node getBlockTemplate latency, and your stale/DOA shares to get a feel for your particular efficiency...
After a few days of mining you can look up your miner in our "active miners" list for p2pool. That estimated hashrate, if higher then expected, means you are mining efficiently/currently lucky. If it is lower then expected you are mining inefficiently or in a streak of bad luck. (this only works after you have been mining for the length of the share chain, i.e. 3 days)
http://minefast.coincadence.com/p2pool-stats.php
Also, node efficiency is a poor indicator on any node with more then 1 miner. A single miner with a high latency can bring node efficiency way down, while your miners may be mining very efficiently.
Look at your latency to the node, the node getBlockTemplate latency, and your stale/DOA shares to get a feel for your particular efficiency...
After a few days of mining you can look up your miner in our "active miners" list for p2pool. That estimated hashrate, if higher then expected, means you are mining efficiently/currently lucky. If it is lower then expected you are mining inefficiently or in a streak of bad luck. (this only works after you have been mining for the length of the share chain, i.e. 3 days)
http://minefast.coincadence.com/p2pool-stats.php
Thanks Windpath. Is node efficiency with perfect miners (the stat) a good indication of the quality of the node? I agree just plain node efficiency can be skewed by individual miners.
I don't think any 1 factor can really determine the quality of a node for a given miner, it's a combination of factors...
The "efficiency with perfect miners" stat simply excludes DOA shares from the "efficiency" stat.
If you have a miner with a high stale/orphan rate it will go down just like the efficiency stat, and could be caused by various problems.
In addition to your latency to the node, the node getBlockTemplate latency, and your stale/DOA shares mentioned above; you would also need to take into account node stability/response time, the number of incoming/outgoing p2pool peers and their latency from the node, and some other factors I'm probably forgetting to really get the whole picture.
There
February 05, 2015, 09:05:24 PM
Don't think of it as competing with miners on the same node, you are completing (and collaborating) with the whole pool.
Also, node efficiency is a poor indicator on any node with more then 1 miner. A single miner with a high latency can bring node efficiency way down, while your miners may be mining very efficiently.
Look at your latency to the node, the node getBlockTemplate latency, and your stale/DOA shares to get a feel for your particular efficiency...
After a few days of mining you can look up your miner in our "active miners" list for p2pool. That estimated hashrate, if higher then expected, means you are mining efficiently/currently lucky. If it is lower then expected you are mining inefficiently or in a streak of bad luck. (this only works after you have been mining for the length of the share chain, i.e. 3 days)
http://minefast.coincadence.com/p2pool-stats.php
Also, node efficiency is a poor indicator on any node with more then 1 miner. A single miner with a high latency can bring node efficiency way down, while your miners may be mining very efficiently.
Look at your latency to the node, the node getBlockTemplate latency, and your stale/DOA shares to get a feel for your particular efficiency...
After a few days of mining you can look up your miner in our "active miners" list for p2pool. That estimated hashrate, if higher then expected, means you are mining efficiently/currently lucky. If it is lower then expected you are mining inefficiently or in a streak of bad luck. (this only works after you have been mining for the length of the share chain, i.e. 3 days)
http://minefast.coincadence.com/p2pool-stats.php
Thanks Windpath. Is node efficiency with perfect miners (the stat) a good indication of the quality of the node? I agree just plain node efficiency can be skewed by individual miners.
February 05, 2015, 06:32:19 PM
Jonny answered back on my whale on the node question. Will it affect the other miners?
Here's his answer:
"Short answer is yes... That miner with 75TH/s is accounted for by the node and it ups the share difficulty. Now, if that miner knows what he's doing, he'll account for it himself by using /xxxx after his address ... Where xxx is a value greater than the typical share difficulty. Example if the share difficulty is 10000000 then that user would do something like ADDRESS/100000000."
Whale, if your watching, do me a favor, would you?
S
Fancy seeing you here. Seeing your post in the thread I realized you're on my node!Here's his answer:
"Short answer is yes... That miner with 75TH/s is accounted for by the node and it ups the share difficulty. Now, if that miner knows what he's doing, he'll account for it himself by using /xxxx after his address ... Where xxx is a value greater than the typical share difficulty. Example if the share difficulty is 10000000 then that user would do something like ADDRESS/100000000."
Whale, if your watching, do me a favor, would you?
S
That jump in hash rate is me... I rented some heavy firepower for a day for fun. It'll be done in about 4 hours or so. The reported rate you're seeing on windpath's node is because I haven't ramped up to the full shares I should have with 95TH/s. I would need to keep that level of hashing up for another few days for it to catch up.
As for your miner, it is hitting a bad luck streak. It is all part and parcel of the way p2pool works. I have an S3 on a node that didn't find a share for 5 days!
February 05, 2015, 06:24:04 PM
For your previous question, yes in the default front end, you would have to click every link.
For the second question, your hashrate is taken into consideration if you do not set pseudo share difficulty, node efficiency is not.
P2Pool share difficulty is dynamically adjusted every 30 seconds with a 30 second share target, it is pool wide, meaning it is the same for all miners regardless of hashrate.
Submitted shares under "share difficulty" are discarded, however they do help provide more accurate stats.
"Pseudo share difficulty", either set by the miner or adjusted by the pool tries to keep a regular, but not overwhelming to the node, amount of shares coming in so that your hashrate can be accurately measured (~1 per second).
For the second question, your hashrate is taken into consideration if you do not set pseudo share difficulty, node efficiency is not.
P2Pool share difficulty is dynamically adjusted every 30 seconds with a 30 second share target, it is pool wide, meaning it is the same for all miners regardless of hashrate.
Submitted shares under "share difficulty" are discarded, however they do help provide more accurate stats.
"Pseudo share difficulty", either set by the miner or adjusted by the pool tries to keep a regular, but not overwhelming to the node, amount of shares coming in so that your hashrate can be accurately measured (~1 per second).
Great, thanks for all the info and support you give to the community. I appreciate it, Most of them who live in assumptions will learn from your posts about p2pool
February 05, 2015, 06:18:47 PM
http://minefast.coincadence.com:9332/static/original/ - In this page, "My shares" shows invalid pages, how do we find the latest share submitted in this node under "my shares"? Opening each link to check the details is a headache job.
But my question above is still being unanswered. Also how does the pool assign actual difficulty of a share to worker? Based on miner hashrate or node efficiency? Is there any connection with the node efficiency and actual share difficulty we get?
I was being told that better the nodes efficiency, higher the difficulty shares it gets from the pool. Or is it just random or luck?
Anyone??? views on this question?
For your previous question, yes in the default front end, you would have to click every link.
For the second question, your hashrate is taken into consideration if you do not set pseudo share difficulty, node efficiency is not.
P2Pool share difficulty is dynamically adjusted every 30 seconds with a 30 second share target, it is pool wide, meaning it is the same for all miners regardless of hashrate.
Submitted shares under "share difficulty" are discarded, however they do help provide more accurate stats.
"Pseudo share difficulty", either set by the miner or adjusted by the pool tries to keep a regular, but not overwhelming to the node, amount of shares coming in so that your hashrate can be accurately measured (~1 per second).
The code is in work.py, starting at line 337:
Code:
if desired_pseudoshare_target is None:
target = 2**256-1
local_hash_rate = self._estimate_local_hash_rate()
if local_hash_rate is not None:
target = min(target,
bitcoin_data.average_attempts_to_target(local_hash_rate * 1))
# limit to 1 share response every second by modulating pseudoshare difficulty
else:
target = desired_pseudoshare_target
target = max(target, share_info['bits'].target)
for aux_work, index, hashes in mm_later:
target = max(target, aux_work['target'])
target = math.clip(target, self.node.net.PARENT.SANE_TARGET_RANGE)
target = 2**256-1
local_hash_rate = self._estimate_local_hash_rate()
if local_hash_rate is not None:
target = min(target,
bitcoin_data.average_attempts_to_target(local_hash_rate * 1))
# limit to 1 share response every second by modulating pseudoshare difficulty
else:
target = desired_pseudoshare_target
target = max(target, share_info['bits'].target)
for aux_work, index, hashes in mm_later:
target = max(target, aux_work['target'])
target = math.clip(target, self.node.net.PARENT.SANE_TARGET_RANGE)
February 05, 2015, 06:05:37 PM
http://minefast.coincadence.com:9332/static/original/ - In this page, "My shares" shows invalid pages, how do we find the latest share submitted in this node under "my shares"? Opening each link to check the details is a headache job.
But my question above is still being unanswered. Also how does the pool assign actual difficulty of a share to worker? Based on miner hashrate or node efficiency? Is there any connection with the node efficiency and actual share difficulty we get?
I was being told that better the nodes efficiency, higher the difficulty shares it gets from the pool. Or is it just random or luck?
Anyone??? views on this question?
February 05, 2015, 05:49:56 PM
http://minefast.coincadence.com:9332/static/original/ - In this page, "My shares" shows invalid pages, how do we find the latest share submitted in this node under "my shares"? Opening each link to check the details is a headache job.
But my question above is still being unanswered. Also how does the pool assign actual difficulty of a share to worker? Based on miner hashrate or node efficiency? Is there any connection with the node efficiency and actual share difficulty we get?
I was being told that better the nodes efficiency, higher the difficulty shares it gets from the pool. Or is it just random or luck?
Anyone??? views on this question?
February 05, 2015, 05:30:44 PM
Jonny answered back on my whale on the node question. Will it affect the other miners?
Here's his answer:
"Short answer is yes... That miner with 75TH/s is accounted for by the node and it ups the share difficulty. Now, if that miner knows what he's doing, he'll account for it himself by using /xxxx after his address ... Where xxx is a value greater than the typical share difficulty. Example if the share difficulty is 10000000 then that user would do something like ADDRESS/100000000."
Whale, if your watching, do me a favor, would you?
S
Here's his answer:
"Short answer is yes... That miner with 75TH/s is accounted for by the node and it ups the share difficulty. Now, if that miner knows what he's doing, he'll account for it himself by using /xxxx after his address ... Where xxx is a value greater than the typical share difficulty. Example if the share difficulty is 10000000 then that user would do something like ADDRESS/100000000."
Whale, if your watching, do me a favor, would you?
S
February 05, 2015, 05:10:27 PM
OK.
I've been on the node for a month.
I suspect my share luck has been off, lately. Nothing, other than the whale, has changed.
I'll relax for a day or so and see what happens.
I think I might fire up my local node again. I had shut it down because I needed the computer for other things, but I may run it and let the node I'm on right now be a backup if I need to take it down occasionally.
Thanks for the help!
S
I've been on the node for a month.
I suspect my share luck has been off, lately. Nothing, other than the whale, has changed.
I'll relax for a day or so and see what happens.
I think I might fire up my local node again. I had shut it down because I needed the computer for other things, but I may run it and let the node I'm on right now be a backup if I need to take it down occasionally.
Thanks for the help!
S
February 05, 2015, 04:56:28 PM
Sounds like 2 extremes (you and the whale)...
The estimate is based on your current payout if a block were found NOW and what % of the total pool hashrate that *should* represent.
If you have not been stably mining for at least the length of the current share chain it will be way off....
The estimate is based on your current payout if a block were found NOW and what % of the total pool hashrate that *should* represent.
If you have not been stably mining for at least the length of the current share chain it will be way off....
February 05, 2015, 04:07:21 PM
Ha. Just looked up the whale's address and its effective hash rate is 25TH/s when the pool is calling out 94 TH/s.
Maybe I should just sit back for a day or so and see what happens..
Is there anything I should look for in my miner status that will indicate something I should change? Is the whale spoiling the node's performance?
400GH/s pretty much screws my electricity efficiency.
Maybe I should just sit back for a day or so and see what happens..
Is there anything I should look for in my miner status that will indicate something I should change? Is the whale spoiling the node's performance?
400GH/s pretty much screws my electricity efficiency.
February 05, 2015, 04:00:28 PM
Yikes. Its giving me a hash rate of 400GH/s when the pool is reporting a 1.4 TH/s rate.
What could be going wrong to result in such an inefficiency? It has been stellar up until the last couple days.. or is it just a bout of bad luck?
Is that what that number is telling me.. how bad my luck has been lately?
Is that number based on the last share cycle (3 days?)
S
What could be going wrong to result in such an inefficiency? It has been stellar up until the last couple days.. or is it just a bout of bad luck?
Is that what that number is telling me.. how bad my luck has been lately?
Is that number based on the last share cycle (3 days?)
S
February 05, 2015, 03:28:12 PM
...
where to you type that?
Im not here to make a million.. I wish. but electricity is not cheap....
where to you type that?
Im not here to make a million.. I wish. but electricity is not cheap....
In the command line when you start P2Pool
Quote
python -O ./run_p2pool.py --address YOUR_ADDRESS --give-author 0 -f FEE_PERCENT ...
February 05, 2015, 03:24:58 PM
Thanks!
How can I access the active miners list for p2pool? Sorry if that's a stupid question.
How can I access the active miners list for p2pool? Sorry if that's a stupid question.
Go here: http://minefast.coincadence.com/p2pool-stats.php
Click on "Active Miners", you can click the header fields to sort....
http://imgur.com/cp5sWJ6
Jump to: