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

gyverlb

hero member

Activity: 896

Merit: 1000

Quote from: maqifrnswa on November 04, 2013, 12:04:44 PM

Quote from: forrestv on October 31, 2013, 06:04:37 PM

I will decrease the percentage then. Maybe 1.67%? That's a share every half hour.

don't know this part of the code well enough, but is the calculation per miner or per node? It's possible a large node may get >1.67% of the shares but be comprised of many small miners. I don't think it's too big of a deal, it would just encourage smaller miners to diversify and not all go on a single node.

If it's like the rest of the code I suppose it should be by payment address. So if your miners all share the same payment address they will share the 1.67%.

maqifrnswa

sr. member

Activity: 454

Merit: 252

Quote from: forrestv on October 31, 2013, 06:04:37 PM

I will decrease the percentage then. Maybe 1.67%? That's a share every half hour.

don't know this part of the code well enough, but is the calculation per miner or per node? It's possible a large node may get >1.67% of the shares but be comprised of many small miners. I don't think it's too big of a deal, it would just encourage smaller miners to diversify and not all go on a single node.

zvs

legendary

Activity: 1680

Merit: 1000

https://web.archive.org/web/*/nogleg.com

Quote from: Jude Austin on November 04, 2013, 02:35:28 AM

BTW, feel free to PM me if you ever decide that you want to increase that 75% efficiency

for example, 84.201.254.19:9332, used to have a 15% orphan rate

zvs

legendary

Activity: 1680

Merit: 1000

https://web.archive.org/web/*/nogleg.com

Quote from: Jude Austin on November 04, 2013, 02:35:28 AM

Quote from: Jude Austin on November 04, 2013, 02:23:25 AM

Quote from: zvs on November 02, 2013, 09:39:00 AM

hetzner network was screwed for about 15m, if anyone reads this that was mining on my pool or some other one located on hetzner network

oh, and luck over the last 3 days has been good if you include 266856 and onwards Grin

5 blocks in 76 hours, estimated time is 14hr30m but that's with 32.9 thash, and the average over the last 76 hours is probably more like 29-30thash... jaja

btw: whoever is using p2pool.org:9332 and paying 2% for 75% efficiency... stop!

Oh thanks.

I don't think your advice is working tho.

1.60TH/s (13% DOA) at this time.

When/if you ever get that hash rate you will see your efficiency drop also.

Does everyone on this forum always get jealous and have to attack everyone else?

It's ok man, some day you too will have miners, but attacking other people isn't going to work.

And another thing, how is your expected BTC in 24 hours increasing when you charge no fee?

you truly have no clue. it's quite sad.

my advice isn't working? huh?

i have been at 1.5thash before, see http://nogleg.com:9332/static/graphs.html?Week

here:

http://nogleg.com:9332/fee
http://p2pool.org:9332/fee

get a grip. good job grabbing p2pool.org and preying on the dim, btw. i see that you're up to 0.03 btc from fees yourself.

by the way, I charge one millions % in fees

that's a lot of monies.

ps: the only p2pool I've ever attacked is yours, and that's because it took you two weeks to upgrade to a p2pool client that supported the NewShare... wasting all those poor souls hashes that happen to be at your site. then again, I suppose you *did* have about a 1/1000 chance per day to solve a block. now it's merely on principle

wtogami

sr. member

Activity: 263

Merit: 250

Hi folks,

https://bitcointalk.org/index.php?topic=320695.0;all
p2pool users may be interested in Bitcoin OMG, the branch of Bitcoin that contains many of the well-tested features from Bitcoin 0.9 and Litecoin 0.8. Two of those features, Disable Wallet mode and phantomcircuit's Faster Propagation may be of interest to p2pool miners in further optimizing their mining node by reducing RAM requirements and getting new blocks a split second faster. Disable Wallet is only usable for headless bitcoind (not bitcoin-qt wallets). Check out the thread for a list of other features. Testing of that branch has already helped to improve Bitcoin 0.9.

Jude Austin

legendary

Activity: 1140

Merit: 1000

The Real Jude Austin

Quote from: Jude Austin on November 04, 2013, 02:23:25 AM

Quote from: zvs on November 02, 2013, 09:39:00 AM

hetzner network was screwed for about 15m, if anyone reads this that was mining on my pool or some other one located on hetzner network

oh, and luck over the last 3 days has been good if you include 266856 and onwards Grin

5 blocks in 76 hours, estimated time is 14hr30m but that's with 32.9 thash, and the average over the last 76 hours is probably more like 29-30thash... jaja

btw: whoever is using p2pool.org:9332 and paying 2% for 75% efficiency... stop!

Oh thanks.

I don't think your advice is working tho.

1.60TH/s (13% DOA) at this time.

When/if you ever get that hash rate you will see your efficiency drop also.

Does everyone on this forum always get jealous and have to attack everyone else?

It's ok man, some day you too will have miners, but attacking other people isn't going to work.

And another thing, how is your expected BTC in 24 hours increasing when you charge no fee?

Mogumodz

sr. member

Activity: 290

Merit: 250

Quote from: oldbushie on November 04, 2013, 01:46:10 AM

I recently added 60 GH/s, so why would my reward suddenly go DOWN instead of up? Worst case, wouldn't it just stay level? o_O I did notice a bit of an increase in total p2pool hashrate, but I wouldn't expect such a big drop in my own payout based on how much it increased by. I did have a little downtime while I was setting up the new miner but said downtime was minimal. All my other stats read normally though. Efficiency is 101% and latency is < 0.1s. "Local rate" and "Local rate reflected in shares" match up with each other for the past 24 hours, as well as matching what I would expect for the combination of the miners I have.

It will pretty much always go up and down over time.

Jude Austin

legendary

Activity: 1140

Merit: 1000

The Real Jude Austin

Quote from: zvs on November 02, 2013, 09:39:00 AM

hetzner network was screwed for about 15m, if anyone reads this that was mining on my pool or some other one located on hetzner network

oh, and luck over the last 3 days has been good if you include 266856 and onwards Grin

5 blocks in 76 hours, estimated time is 14hr30m but that's with 32.9 thash, and the average over the last 76 hours is probably more like 29-30thash... jaja

btw: whoever is using p2pool.org:9332 and paying 2% for 75% efficiency... stop!

Oh thanks.

I don't think your advice is working tho.

1.60TH/s (13% DOA) at this time.

When/if you ever get that hash rate you will see your efficiency drop also.

Does everyone on this forum always get jealous and have to attack everyone else?

It's ok man, some day you too will have miners, but attacking other people isn't going to work.

oldbushie

member

Activity: 94

Merit: 10

I recently added 60 GH/s, so why would my reward suddenly go DOWN instead of up? Worst case, wouldn't it just stay level? o_O I did notice a bit of an increase in total p2pool hashrate, but I wouldn't expect such a big drop in my own payout based on how much it increased by. I did have a little downtime while I was setting up the new miner but said downtime was minimal. All my other stats read normally though. Efficiency is 101% and latency is < 0.1s. "Local rate" and "Local rate reflected in shares" match up with each other for the past 24 hours, as well as matching what I would expect for the combination of the miners I have.

zvs

legendary

Activity: 1680

Merit: 1000

https://web.archive.org/web/*/nogleg.com

Quote from: Mogumodz on November 03, 2013, 10:52:39 AM

@zvs

Ha....ha....ha

"Nigerian BTC P2Pool - "We mine our Bitcoin directly out of other people's wallets!"

i thought it was fitting Grin

Mogumodz

sr. member

Activity: 290

Merit: 250

@zvs

Ha....ha....ha

"Nigerian BTC P2Pool - "We mine our Bitcoin directly out of other people's wallets!"

zvs

legendary

Activity: 1680

Merit: 1000

https://web.archive.org/web/*/nogleg.com

Quote

Has this been implemented yet? I'm considering turning my node back on to see if it improves anything..... Grin

nothing on git yet... there were two changes, but only affecting litecoins and some other bizarre coin (terracoins?)

IYFTech

hero member

Activity: 686

Merit: 500

WANTED: Active dev to fix & re-write p2pool in C

Quote from: forrestv on October 31, 2013, 06:04:37 PM

Quote from: gyverlb on October 31, 2013, 04:53:51 PM

Quote from: lenny_ on October 31, 2013, 04:40:20 PM

So nice it has been implemented already. But I will agree with comments made earlier on, it should be applied to miners with 500 GH/s (1.7% of total p2pool hashrate). Please reduce it to at least 2% from 5%. It's a simple fix, and it will help a lot to small miners.

From experience, having "only" 2% of the p2pool hashrate doesn't mean there's too much variance (the rewards oscillate +/-~10% around).

With 5%, ~20 large miners can take most of the pie, leaving crumbs to others. With 2%, this is raised to 50 large miners.

I'd be OK with a 1% limit, but 2% should limit complains of high variance from large miners (the reward may even move as much from the hashrate fluctuations of the whole pool as from the share frequency variance, people with 5% or more may be able to confirm this if they have variance around 10% in their rewards too).

BTW: I've not looked into the code, what would happen if there were only 10 miners on p2pool? Is the current algorithm able to converge on sane values or would the current 5% target raise the individual share difficulty without bonds.
From the one-liner extract above it seems there's a missing parameter to achieve this protection (the number of distinct addresses with valid shares in the recent sharechain).

I will decrease the percentage then. Maybe 1.67%? That's a share every half hour.

If there are very few miners, nothing insane happens.

Each miner's share difficulty multiplier becomes the maximum, 30, and then the 30-second share period target decreases the minimum difficulty until there's a share every 30 seconds again.

Has this been implemented yet? I'm considering turning my node back on to see if it improves anything..... Grin

zvs

legendary

Activity: 1680

Merit: 1000

https://web.archive.org/web/*/nogleg.com

Quote from: gnar1ta$ on November 02, 2013, 11:33:50 PM

Quote from: zvs on November 02, 2013, 11:10:24 PM

Just a heads up that from the 40 nodes I can see right now; 24.161.35.225, 184.56.251.69, 183.136.216.39, 24.10.44.25, 183.136.216.39, 95.128.48.209, 193.190.255.150, 38.109.218.101, 198.91.172.112, 209.195.4.74, 186.220.27.239 all have over 1MB of transactions stored (while most everyone else in this lot has 45kb). That's why your bitcoind latency is so high. Some of these nodes are essentially dead, but others aren't...

Upgrade your bitcoind version, you're probably picking up the horse staple battery transactions... or lower maxblocksize to something like 250000...

oh, btw, 24.161.35.225... very impressive system there, the other five I looked at had latencies from 2s to 6s, yours is hanging out around 0.9s...

Where do you find all this information?

www.nogleg.com:9332/peer_txpool_sizes

Look in the p2ool/web.py file and you'll find all the things you can query. ed: I pulled that earlier list off my other server that I use as a relay, it connects to 40 random nodes, w/o using --p2pool-node, so it tends to get a bunch of duds; p2pool nodes that haven't been updated in a couple of months.

Quote

zvs ,You seem to be really switched on , I was wondering what would cause the spike in latency in my graph.

I'm honestly not sure about those. My guess would be that it's a large transaction that's being forwarded to your p2pool to store, but I'm not sure.... think it also occurs occasionally when blocks are solved. The gradual increase is normal the longer it goes w/o a block being solved (all these transactions being stored)....

Now, my question... why does it report a much larger DOA rate in my log file www.nogleg.com/log then it does on the website?

www.nogleg.com:9332/static

Also, is there some significant drawback to submitting a share twice? I assume the second (or third or fourth) counts as a DOA, but ... wouldn't really be a DOA, since the first one would be the one that mattered?

Is that why there's like a 20% discrepency between the DOA in the log and the DOA on the website?

ED#10: good lord, ok, everything fixed. now, anyone know the answer to the question?

Polyatomic

sr. member

Activity: 257

Merit: 250

zvs ,You seem to be really switched on , I was wondering what would cause the spike in latency in my graph.

gnar1ta$

donator

Activity: 798

Merit: 500

Quote from: zvs on November 02, 2013, 11:10:24 PM

Just a heads up that from the 40 nodes I can see right now; 24.161.35.225, 184.56.251.69, 183.136.216.39, 24.10.44.25, 183.136.216.39, 95.128.48.209, 193.190.255.150, 38.109.218.101, 198.91.172.112, 209.195.4.74, 186.220.27.239 all have over 1MB of transactions stored (while most everyone else in this lot has 45kb). That's why your bitcoind latency is so high. Some of these nodes are essentially dead, but others aren't...

Upgrade your bitcoind version, you're probably picking up the horse staple battery transactions... or lower maxblocksize to something like 250000...

oh, btw, 24.161.35.225... very impressive system there, the other five I looked at had latencies from 2s to 6s, yours is hanging out around 0.9s...

Where do you find all this information?

zvs

legendary

Activity: 1680

Merit: 1000

https://web.archive.org/web/*/nogleg.com

Just a heads up that from the 40 nodes I can see right now; 24.161.35.225, 184.56.251.69, 183.136.216.39, 24.10.44.25, 183.136.216.39, 95.128.48.209, 193.190.255.150, 38.109.218.101, 198.91.172.112, 209.195.4.74, 186.220.27.239 all have over 1MB of transactions stored (while most everyone else in this lot has 45kb). That's why your bitcoind latency is so high. Some of these nodes are essentially dead, but others aren't...

Upgrade your bitcoind version, you're probably picking up the horse staple battery transactions... or lower maxblocksize to something like 250000...

oh, btw, 24.161.35.225... very impressive system there, the other five I looked at had latencies from 2s to 6s, yours is hanging out around 0.9s...

SpAcEDeViL

legendary

Activity: 986

Merit: 1027

Miner-Control.de Pooler

Hy,

i dont know... can i set the p2pool node to a pool node for p2pool network?

So the Miner makes shares for the Node, and when there enough shares, they make a p2pool network share.

All Miners on the node become % of the share. based on there shares to the node.

p2pool payout to the node wallet, and a option for weekly payouts, or the miner can set it over there user name.

e.g. : *Bitcoin-Wallet*/+P0.1 for Payout when the miner have 0.1 btc

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: Mogumodz on November 02, 2013, 03:42:26 PM

Quote from: mdude77 on November 02, 2013, 11:31:52 AM

Quote from: zvs on November 02, 2013, 09:39:00 AM

hetzner network was screwed for about 15m, if anyone reads this that was mining on my pool or some other one located on hetzner network

oh, and luck over the last 3 days has been good if you include 266856 and onwards Grin

5 blocks in 76 hours, estimated time is 14hr30m but that's with 32.9 thash, and the average over the last 76 hours is probably more like 29-30thash... jaja

btw: whoever is using p2pool.org:9332 and paying 2% for 75% efficiency... stop!

I second that! I've got my measily 12gh/s pointed to zvs's server and it's working pretty well. I gave up trying to run my own, don't have the bandwidth for it. Sad

(btw - thanks zvs!!)

M

Heh, I think that must of been you who connected to my pool for a few minuites then

That'd probably be me. I have another pool setup as backup. Must be yours.

M

Mogumodz

sr. member

Activity: 290

Merit: 250

Quote from: zvs on November 02, 2013, 03:47:24 PM

Quote from: Mogumodz on November 02, 2013, 03:42:26 PM

Quote from: mdude77 on November 02, 2013, 11:31:52 AM

Quote from: zvs on November 02, 2013, 09:39:00 AM

hetzner network was screwed for about 15m, if anyone reads this that was mining on my pool or some other one located on hetzner network

oh, and luck over the last 3 days has been good if you include 266856 and onwards Grin

5 blocks in 76 hours, estimated time is 14hr30m but that's with 32.9 thash, and the average over the last 76 hours is probably more like 29-30thash... jaja

btw: whoever is using p2pool.org:9332 and paying 2% for 75% efficiency... stop!

I second that! I've got my measily 12gh/s pointed to zvs's server and it's working pretty well. I gave up trying to run my own, don't have the bandwidth for it. Sad

(btw - thanks zvs!!)

M

Heh, I think that must of been you who connected to my pool for a few minuites then

ah, nice to have backup pools set. i think you have the wrong person though, since if you look at my weekly chart, FTX has been on it for 3 or 4 days =p

Yeah, the top chart is your pools stats, I was just showing the chunk where it was blank and was on my pool it seems.

I was confused more than anything who it was Cheesy

I have also set up a private p2pool node on Azure testing a Mercury which is running very nicely atm.

Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 471. (Read 2591928 times)