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

[NothinG]

So, I take it there really isn't a point for me to mine at P2Pool anymore until I gather more Gh/s?

[rav3n_pl]

So, I take it there really isn't a point for me to mine at P2Pool anymore until I gather more Gh/s?

Why not? Every share is valid up to 3 days or 3 blocks. It is not really matter you mine there or any other pool. Your payout will be always proportional to pool power and network power.
This what make P2pool better than other pools is lower fee (mostly 0-1%), full tx fee payout and ddos resistance (it it decentralized).

[mdude77]

So, I take it there really isn't a point for me to mine at P2Pool anymore until I gather more Gh/s?

Can still mine, you'll still get something.  Your variance will be high though.  And it'll be higher after the next skyrocket difficulty increase due in about 6 hours.

M

[NothinG]

I'll leave my stuff pointed @ p2pool just because of decentralization.

[zvs]

some of these places will get lots more orphans now that i took 3 relays down ,

dunno why nobody makes proper use of p2pool-node

[zvs]

the thing seems to scale up too much?  the 2.3m for 1CzLSNz7V6EufECrjvMXBiVo8Tu7z3XgkF seems excessive

[zvs]

the thing seems to scale up too much?  the 2.3m for 1CzLSNz7V6EufECrjvMXBiVo8Tu7z3XgkF seems excessive

eh, i am restarting my stuff to help whoever that is at 195.72.200.193

hah, 30 seconds later

Time first seen: Tue Nov 05 2013 06:54:22 GMT-0600 (Central Standard Time) (1383656062.61601)
Peer first received from: 195.72.200.193,9333
Share data
Timestamp: Tue Nov 05 2013 06:53:19 GMT-0600 (Central Standard Time) (1383655999)
Difficulty: 1845505.3058484078
Minimum difficulty: 147544.50316789394
Payout address: 1CzLSNz7V6EufECrjvMXBiVo8Tu7z3XgkF


+3

now some *90 minutes later, 22-3-3 is much better than the 10-3-2 or whatever it was before

[zvs]

there's a serious issue w/ propagation here, too many big miners on private nodes, probably with the default random 6 connections.

28 out of the last 30 shares received by 195.72.200.193 came from one of my 3 nodes, which I just restarted 90m ago...  195.72.200.193 is running @ 5thash.  It had 5 incoming connections, 9 good shares, 2 orphans, 3 doa after running for an hour.

WTF does it only have 5 incoming connections for?   I bet 2 or 3 of those were even just random connections.  Maybe 2 or 3 on --p2pool-node?  that's just absurd

then again, I guess p2pool is a bit of a microcosm of the bigger pools, right?  so it's good for the 5thash pool to get lots of orphans and DOAs?  shrug.

if you want to improve your own efficiency rating, --p2pool-node 5.9.24.81 and --p2pool-node 198.12.127.2 ..  they are hashing at a combined 8ghash right now, so it doesn't benefit those specific pools in any meaningful way

for any other person that does,  the person that doesn't loses efficiency relative to that person & hence to the pool as a whole (or at least until some get DDoSed again)

[gnar1ta$]

One of our Jupiters is hashing well currently on P2Pool using the latest firmware.  We're going to leave it on there for twenty-four hours and if all is well put both on there.  Which should add ~1.1TH/s to the pool.

Can you share your node address so we can see stats, and paste cgminer output from Jupiter? I am curious how you can say "it's hashing well" when AFAIK KNC firmware is still doing full stop for 2-3sec everytime when LP/work restart arrives, lol.

The .98 firmware and cgminer 3.6.6 solved the horrible work restarts.  KNC's do work well on p2pool now.  I restarted recently, but here is about a 12 hr run.  The cgminer hashrate displays lower than the pool average reports - so don't take that as the true rate.  I average around 520GH/s on my node stats page, that's what I'm paid on right?

Code:

2013-11-05 10:27:48.573721  Pool: 38534GH/s Stale rate: 19.5% Expected time to block: 12.1 hours
2013-11-05 10:27:51.588785 P2Pool: 17319 shares in chain (17323 verified/17323 total) Peers: 23 (17 incoming)
2013-11-05 10:27:51.589007  Local: 494GH/s in last 10.0 minutes Local dead on arrival: ~4.6% (3-7%) Expected time to share: 24.1 minutes
2013-11-05 10:27:51.589132  Shares: 36 (3 orphan, 0 dead) Stale rate: ~8.3% (2-22%) Efficiency: ~113.8% (97-121%) Current payout: 0.3551 BTC

Code:

cgminer version 3.6.6 - Started: [2013-11-05 03:25:31]
--------------------------------------------------------------------------------
 (5s):560.6G (avg):472.1Gh/s | A:5110528  R:117504  HW:297721  WU:7295.2/m
 ST: 1  SS: 3  NB: 89  LW: 7667747  GF: 1  RF: 0
 Connected to 24.173.129.247 diff 128 with stratum as user Jupiter+128
 Block: 0000856c4a884be0...  Diff:391M  Started: [15:20:37]  Best share: 1.51M
--------------------------------------------------------------------------------
 [P]ool management [S]ettings [D]isplay options [Q]uit
 KnC 0:                | 601.4G/472.1Gh/s | A:5110528 R:117504 HW:297721 WU: 7295.2/m
--------------------------------------------------------------------------------

 [2013-11-05 15:28:58] Accepted 00f0fbf9 Diff 271/128 KnC 0 pool 0
 [2013-11-05 15:28:58] Accepted 01ad75f9 Diff 152/128 KnC 0 pool 0
 [2013-11-05 15:29:00] Accepted 00c26124 Diff 337/128 KnC 0 pool 0
 [2013-11-05 15:29:01] Accepted 01b8facc Diff 148/128 KnC 0 pool 0
 [2013-11-05 15:29:02] Accepted 00da070a Diff 300/128 KnC 0 pool 0
 [2013-11-05 15:29:02] Accepted 0082729e Diff 502/128 KnC 0 pool 0
 [2013-11-05 15:29:03] Accepted 00bc1667 Diff 348/128 KnC 0 pool 0
 [2013-11-05 15:29:05] Accepted 0162889c Diff 184/128 KnC 0 pool 0
 [2013-11-05 15:29:06] KnC: core 2-64 was enabled back from disabled state
 [2013-11-05 15:29:06] Accepted 00136d41 Diff 3.37K/128 KnC 0 pool 0
 [2013-11-05 15:29:06] Accepted 004a7296 Diff 880/128 KnC 0 pool 0
 [2013-11-05 15:29:07] KnC: core 2-82 was enabled back from disabled state
 [2013-11-05 15:29:08] Stratum from pool 0 requested work restart
 [2013-11-05 15:29:08] KnC running flushwork
 [2013-11-05 15:29:09] Accepted 018eec8a Diff 164/128 KnC 0 pool 0
 [2013-11-05 15:29:09] Accepted 01d02268 Diff 141/128 KnC 0 pool 0
 [2013-11-05 15:29:10] Accepted 0188e0ca Diff 166/128 KnC 0 pool 0
 [2013-11-05 15:29:10] Accepted 016bb15a Diff 180/128 KnC 0 pool 0

[zvs]

Total
Area: 639PH

orphan
Area: 15.4PH (2.4% total)

8.33% is high orphan rate that can be fixed rather easily, that fellow in Taiwan that runs a node has a 7.34% orphan rate over 1648 shares

anyone in western or eastern europe (also including novgorod and basically anything else west of that) should be at 5% or less

i guess 36 shares isn't a very large sample though, maybe just got unlucky with the, uh, pot luck block switches

[zvs]

 it's strange when i look at all these european nodes and they're all at 7%+ orphan rate,  yet only 3 ppl  have even ever asked me about how to fix this

though i'd say it requires more like 8 outgoing connections to be a sure thing

[SpAcEDeViL]

Hoe? Whats up in the network?

I become now many Rejected s ?

And the output changes??

Code:

[2013-11-05 22:42:04] Accepted 0b02017e Diff 23/10 AMU 25 pool 0  <-00000001.acc6dd6e M:P D:10.000 G:22:41:52:0.052 C:9.970 (-1383687712.334) W:1383687724.441 (0.002) S:0.053 R:22:42:04
 [2013-11-05 22:42:06] Rejected 11a44206 Diff 15/10 AMU 1 pool 0  <-00000001.acc6dd6e M:P D:10.000 G:22:41:52:0.052 C:7.633 (-1383687712.334) W:1383687726.276 (0.002) S:0.064 R:22:42:06
 [2013-11-05 22:42:07] Rejected 0186c434 Diff 168/10 AMU 23 pool 0  <-00000001.acc6dd6e M:P D:10.000 G:22:41:52:0.052 C:6.865 (-1383687712.334) W:1383687727.014 (0.002) S:0.076 R:22:42:07
 [2013-11-05 22:42:10] Rejected 0b6f31e9 Diff 22/10 AMU 22 pool 0  <-00000001.acc6dd6e M:P D:10.000 G:22:41:52:0.052 C:10.681 (-1383687712.334) W:1383687730.803 (0.001) S:0.059 R:22:42:10
 [2013-11-05 22:42:12] Rejected 0d3fc2a8 Diff 19/10 AMU 32 pool 0  <-00000001.acc6dd6e M:P D:10.000 G:22:41:52:0.052 C:10.704 (-1383687712.334) W:1383687732.111 (0.005) S:0.059 R:22:42:12
 [2013-11-05 22:42:15] Rejected 129b1ccb Diff 14/10 AMU 11 pool 0  <-00000001.acc6dd6e M:P D:10.000 G:22:41:52:0.052 C:14.013 (-1383687712.334) W:1383687735.873 (0.003) S:0.088 R:22:42:15
 [2013-11-05 22:42:16] Rejected 10b5e94e Diff 15/10 AMU 10 pool 0  <-00000001.acc6dd6e M:P D:10.000 G:22:41:52:0.052 C:21.693 (-1383687712.334) W:1383687736.268 (0.003) S:0.073 R:22:42:16
 [2013-11-05 22:42:16] Rejected 08deaf96 Diff 29/10 AMU 10 pool 0  <-00000001.acc6dd6e M:P D:10.000 G:22:41:52:0.052 C:23.747 (-1383687712.334) W:1383687736.317 (0.008) S:0.070 R:22:42:16
 [2013-11-05 22:42:17] Rejected 0cdf1bfb Diff 20/10 AMU 6 pool 0  <-00000001.acc6dd6e M:P D:10.000 G:22:41:52:0.052 C:22.305 (-1383687712.334) W:1383687737.667 (0.002) S:0.067 R:22:42:17
 [2013-11-05 22:42:20] Rejected 11e593d7 Diff 14/10 AMU 16 pool 0  <-00000001.acc6dd6e M:P D:10.000 G:22:41:52:0.052 C:19.162 (-1383687712.334) W:1383687740.021 (0.002) S:0.074 R:22:42:20

[zvs]

Hoe? Whats up in the network?

I become now many Rejected s ?

And the output changes??

Code:

[2013-11-05 22:42:04] Accepted 0b02017e Diff 23/10 AMU 25 pool 0  <-00000001.acc6dd6e M:P D:10.000 G:22:41:52:0.052 C:9.970 (-1383687712.334) W:1383687724.441 (0.002) S:0.053 R:22:42:04
 [2013-11-05 22:42:06] Rejected 11a44206 Diff 15/10 AMU 1 pool 0  <-00000001.acc6dd6e M:P D:10.000 G:22:41:52:0.052 C:7.633 (-1383687712.334) W:1383687726.276 (0.002) S:0.064 R:22:42:06
 [2013-11-05 22:42:07] Rejected 0186c434 Diff 168/10 AMU 23 pool 0  <-00000001.acc6dd6e M:P D:10.000 G:22:41:52:0.052 C:6.865 (-1383687712.334) W:1383687727.014 (0.002) S:0.076 R:22:42:07
 [2013-11-05 22:42:10] Rejected 0b6f31e9 Diff 22/10 AMU 22 pool 0  <-00000001.acc6dd6e M:P D:10.000 G:22:41:52:0.052 C:10.681 (-1383687712.334) W:1383687730.803 (0.001) S:0.059 R:22:42:10
 [2013-11-05 22:42:12] Rejected 0d3fc2a8 Diff 19/10 AMU 32 pool 0  <-00000001.acc6dd6e M:P D:10.000 G:22:41:52:0.052 C:10.704 (-1383687712.334) W:1383687732.111 (0.005) S:0.059 R:22:42:12
 [2013-11-05 22:42:15] Rejected 129b1ccb Diff 14/10 AMU 11 pool 0  <-00000001.acc6dd6e M:P D:10.000 G:22:41:52:0.052 C:14.013 (-1383687712.334) W:1383687735.873 (0.003) S:0.088 R:22:42:15
 [2013-11-05 22:42:16] Rejected 10b5e94e Diff 15/10 AMU 10 pool 0  <-00000001.acc6dd6e M:P D:10.000 G:22:41:52:0.052 C:21.693 (-1383687712.334) W:1383687736.268 (0.003) S:0.073 R:22:42:16
 [2013-11-05 22:42:16] Rejected 08deaf96 Diff 29/10 AMU 10 pool 0  <-00000001.acc6dd6e M:P D:10.000 G:22:41:52:0.052 C:23.747 (-1383687712.334) W:1383687736.317 (0.008) S:0.070 R:22:42:16
 [2013-11-05 22:42:17] Rejected 0cdf1bfb Diff 20/10 AMU 6 pool 0  <-00000001.acc6dd6e M:P D:10.000 G:22:41:52:0.052 C:22.305 (-1383687712.334) W:1383687737.667 (0.002) S:0.067 R:22:42:17
 [2013-11-05 22:42:20] Rejected 11e593d7 Diff 14/10 AMU 16 pool 0  <-00000001.acc6dd6e M:P D:10.000 G:22:41:52:0.052 C:19.162 (-1383687712.334) W:1383687740.021 (0.002) S:0.074 R:22:42:20

would have to see more of the log to know about the rejected stuff

the output changes, i dunno, ive never seen anything like that.  i turned off all p2pools again like 3 hrs ago though.  is it some new git version?

[gogxmagog]

I'm about to install the bitcoin-qt client on the computer i'm running my miner through, I guess it takes a few days now... will it impair the efficiency of my asic machine?
I want to join p2pool but I have one computer I work on, and one that does the mining (which I had to replace recently - thus - no client  ).  

[rav3n_pl]

You can use any public node you find, just use ur payout address as username.
Try ping to find node closest to you.

[HellDiverUK]

I'm about to install the bitcoin-qt client on the computer i'm running my miner through, I guess it takes a few days now... will it impair the efficiency of my asic machine?
I want to join p2pool but I have one computer I work on, and one that does the mining (which I had to replace recently - thus - no client  ).  

If your machine is reasonably fast, it can run P2Pool, your miners, the lot.  Anything with an i3 or better is fine.

[mdude77]

I'm about to install the bitcoin-qt client on the computer i'm running my miner through, I guess it takes a few days now... will it impair the efficiency of my asic machine?
I want to join p2pool but I have one computer I work on, and one that does the mining (which I had to replace recently - thus - no client  ).  

If your machine is reasonably fast, it can run P2Pool, your miners, the lot.  Anything with an i3 or better is fine.

The main restriction with running your own node is bandwidth.  The average DSL connection can't provide what p2pool and bitcoin need to keep your stale rate low.

M

[gyverlb]

I'm about to install the bitcoin-qt client on the computer i'm running my miner through, I guess it takes a few days now... will it impair the efficiency of my asic machine?
I want to join p2pool but I have one computer I work on, and one that does the mining (which I had to replace recently - thus - no client  ).  

If your machine is reasonably fast, it can run P2Pool, your miners, the lot.  Anything with an i3 or better is fine.

The main restriction with running your own node is bandwidth.  The average DSL connection can't provide what p2pool and bitcoin need to keep your stale rate low.

M

You should define what the average DSL connection is (this changes wildly between countries). I have what I consider one (in my country >10/1 Mbps ADSL connections are common) and I don't have any problem with my stale rate (obviously I changed the default settings of both bitcoind and p2pool).

[zvs]

I'm about to install the bitcoin-qt client on the computer i'm running my miner through, I guess it takes a few days now... will it impair the efficiency of my asic machine?
I want to join p2pool but I have one computer I work on, and one that does the mining (which I had to replace recently - thus - no client   ).  

If your machine is reasonably fast, it can run P2Pool, your miners, the lot.  Anything with an i3 or better is fine.

The main restriction with running your own node is bandwidth.  The average DSL connection can't provide what p2pool and bitcoin need to keep your stale rate low.

M

You should define what the average DSL connection is (this changes wildly between countries). I have what I consider one (in my country >10/1 Mbps ADSL connections are common) and I don't have any problem with my stale rate (obviously I changed the default settings of both bitcoind and p2pool).

or so you say...  You should define what you consider a problematic stale rate.

re: gogxmagog - the cost of running a node locally can possibly offset any fees or extra DOA incurred by pointing at a public node instead, depending on the cost of your elec and if you normally keep that system running 24/7, I guess.  I can mine @ a 200ms latency node and get about 2% DOA.  Dunno what ASIC you have, some of them have a few seconds latency, which would be useless w/ p2pool.  Some don't.

re: my PMs, I'll answer them a little bit later

[shogunmark]

is it normal to always only have 6 out connections? i mean, every once in a while i will see 7 or 8, but the majority of the time its only 6.

Im trying to find ways to really improve performance. I had an older machine running my node with just ubuntu server, but my efficiency was terrible, less than 80% after 48 hours. So i switched up to my windows laptop and currently running over 100% at just under 48 hours. my latency has also decreased. but i have only produced 1 share with 13gh/s. When i was running on my slower server i had produced nearly 5 shares 1 orphan in 48 hours.

I just think something is wrong here but i cant pinpoint it.

71.91.202.165:9332 is my node running on a 30Mbps cable connection.