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

[bhanu545]

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.

Thanks Mdude77 and windpath for all the support.

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?

[1713539876]

1713539876

[1713539876]

1713539876

[1713539876]

1713539876

[1713539876]

1713539876

[1713539876]

1713539876

[1713539876]

1713539876

[kano]

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.

Thanks Mdude77 and windpath for all the support.

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?

the user hash rate is like any pool - it assigns it based on the submitted pseudo shares

[windpath]

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.

Thanks Mdude77 and windpath for all the support.

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)

[bhanu545]

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).

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  

[jonnybravo0311]

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!

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!

[mahrens917]

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

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.

[windpath]

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

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 is must be a great formula to weight and calculate all this and put it in simple terms, I just don't know it

[sEpuLchEr]

Another block and more donations.

Thank you very much!

[Songminer]

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!

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.

[aurel57]

The Chicago node that I am using pings at 51ms.  Can I expect to do much better running my own node?

[mdude77]

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

[PatMan]

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! 

[DiCE1904]

long live p2pool

[sEpuLchEr]

Oh wow. Another donation!

Thank you!!!!

[CptTripps]

You'll always do better with your own node.

EDIT: assuming you have the bandwidth for it.

Question on this...

What kind of sustained bandwidth does a normal mining operation consume? I have a 30MB up/down pipe and was wondering what I should allocate. I can build a DMZ for my local P2Pool server to run on, and set the limits on bandwidth. Would 2MB be enough? More?

[windpath]

You'll always do better with your own node.

EDIT: assuming you have the bandwidth for it.

Question on this...

What kind of sustained bandwidth does a normal mining operation consume? I have a 30MB up/down pipe and was wondering what I should allocate. I can build a DMZ for my local P2Pool server to run on, and set the limits on bandwidth. Would 2MB be enough? More?

Almost a negligible amount...

My node, with 35 peers and a bunch of miners averages around 20kB/s

http://imgur.com/4f3P2l9

[Prelude]

A big thank you to whoever has been donating lately!

[aurel57]

A big thank you to whoever has been donating lately!

I agree Thank You!

[mdude77]

You'll always do better with your own node.

EDIT: assuming you have the bandwidth for it.

Question on this...

What kind of sustained bandwidth does a normal mining operation consume? I have a 30MB up/down pipe and was wondering what I should allocate. I can build a DMZ for my local P2Pool server to run on, and set the limits on bandwidth. Would 2MB be enough? More?

You have tons of bandwidth.  I'm able to do pretty well with 3MB down and 768k up, as long as I only use Bitcoin.  When I start merge mining, I get problems because of bandwidth issues.

M

[MyRig]

30mbps should be good enough if you are trying to use it on multi PH operation.  If you want to install IP came for the security camera watching and VPN from outside, then you may use 7-10Mbps temporary for the access and another 2-5Mpbs for the video watching or playing with your drone flying over the mining farm.

You'll always do better with your own node.

EDIT: assuming you have the bandwidth for it.

Question on this...

What kind of sustained bandwidth does a normal mining operation consume? I have a 30MB up/down pipe and was wondering what I should allocate. I can build a DMZ for my local P2Pool server to run on, and set the limits on bandwidth. Would 2MB be enough? More?