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

[spiccioli]

Well, I've restarted p2pool this morning at 0900 GMT+1, tomorrow I'll let you know what numbers I see.

regards.

spiccioli

Here we are, 20 hours later,

Code:

09:35:21.192503 GOT SHARE! cccccc 2a50469e prev ee4e3887 age 28.24s DEAD ON ARRIVAL
10:51:29.609170 GOT SHARE! cccccc ae20489a prev f5036a0c age 22.39s DEAD ON ARRIVAL
11:00:45.274799 GOT SHARE! cccccc 7ae24ef4 prev b1d8d61a age 20.28s DEAD ON ARRIVAL
11:30:42.989054 GOT SHARE! cccccc 1fb89a27 prev 0af6c699 age 29.78s DEAD ON ARRIVAL
11:38:33.196739 GOT SHARE! cccccc 2ffce415 prev 2c561f75 age 20.60s DEAD ON ARRIVAL
12:20:52.215387 GOT SHARE! cccccc 2deeb628 prev 21ff2b7b age 13.81s DEAD ON ARRIVAL
13:40:47.230481 GOT SHARE! cccccc 1aef7202 prev 1c4d5fe3 age 20.82s
14:27:05.064232 GOT SHARE! cccccc 61749cce prev fc90b812 age 23.00s DEAD ON ARRIVAL
14:54:32.934686 GOT SHARE! cccccc bf2761d7 prev 36614893 age 23.06s
15:13:35.412215 GOT SHARE! cccccc 7981f9dc prev eab26f20 age 20.23s DEAD ON ARRIVAL
15:19:06.171630 GOT SHARE! cccccc f46aa885 prev f98f68d2 age 21.07s DEAD ON ARRIVAL
16:28:33.961269 GOT SHARE! cccccc a9dbaaf4 prev 4f3bac03 age 22.01s DEAD ON ARRIVAL
16:43:18.028367 GOT SHARE! cccccc b2ab8707 prev 881e93ba age 21.55s DEAD ON ARRIVAL
16:48:31.739828 GOT SHARE! cccccc 3231a5e2 prev 08075e20 age 34.50s DEAD ON ARRIVAL
17:11:56.867175 GOT SHARE! cccccc fd25a9bd prev 69d47462 age 26.91s DEAD ON ARRIVAL
17:26:35.194804 GOT SHARE! cccccc 640e9ebd prev 5c2e2221 age 11.85s
17:35:39.829151 GOT SHARE! cccccc 582b0db9 prev f452f2f8 age 16.75s
17:41:35.629520 GOT SHARE! cccccc bd41d585 prev 32818a48 age 33.79s DEAD ON ARRIVAL
17:48:58.909271 GOT SHARE! cccccc ee2d6b93 prev 47bb9cfa age 9.51s
19:13:12.722993 GOT SHARE! cccccc 8ef4140e prev a402ee4a age 11.58s DEAD ON ARRIVAL
19:13:50.677687 GOT SHARE! cccccc f09c4eab prev d0613a01 age 28.44s DEAD ON ARRIVAL
19:15:47.942192 GOT SHARE! cccccc f81a2d80 prev 59599851 age 16.00s DEAD ON ARRIVAL

something is wrong, isn't it?  most are dead, and what does that "age" field really mean?

I'm using latest cgminer 2.2.1 on my miner, with I 7 (intensity) and just p2pool, I have a failover pool, to be honest, but with

Code:

"failover-only" : true

inside cgminer.conf.

Any idea?

best regards.

spiccioli.

[Red Emerald]

Any idea?

What version of p2pool are you running? That looks like miner output. What does your p2pool output look like?

As has been said many times, stales in p2pool are higher than a traditional pool

[eja]

Well, I've restarted p2pool this morning at 0900 GMT+1, tomorrow I'll let you know what numbers I see.

regards.

spiccioli

Here we are, 20 hours later,

Code:

09:35:21.192503 GOT SHARE! cccccc 2a50469e prev ee4e3887 age 28.24s DEAD ON ARRIVAL
10:51:29.609170 GOT SHARE! cccccc ae20489a prev f5036a0c age 22.39s DEAD ON ARRIVAL
11:00:45.274799 GOT SHARE! cccccc 7ae24ef4 prev b1d8d61a age 20.28s DEAD ON ARRIVAL
11:30:42.989054 GOT SHARE! cccccc 1fb89a27 prev 0af6c699 age 29.78s DEAD ON ARRIVAL
11:38:33.196739 GOT SHARE! cccccc 2ffce415 prev 2c561f75 age 20.60s DEAD ON ARRIVAL
12:20:52.215387 GOT SHARE! cccccc 2deeb628 prev 21ff2b7b age 13.81s DEAD ON ARRIVAL
13:40:47.230481 GOT SHARE! cccccc 1aef7202 prev 1c4d5fe3 age 20.82s
14:27:05.064232 GOT SHARE! cccccc 61749cce prev fc90b812 age 23.00s DEAD ON ARRIVAL
14:54:32.934686 GOT SHARE! cccccc bf2761d7 prev 36614893 age 23.06s
15:13:35.412215 GOT SHARE! cccccc 7981f9dc prev eab26f20 age 20.23s DEAD ON ARRIVAL
15:19:06.171630 GOT SHARE! cccccc f46aa885 prev f98f68d2 age 21.07s DEAD ON ARRIVAL
16:28:33.961269 GOT SHARE! cccccc a9dbaaf4 prev 4f3bac03 age 22.01s DEAD ON ARRIVAL
16:43:18.028367 GOT SHARE! cccccc b2ab8707 prev 881e93ba age 21.55s DEAD ON ARRIVAL
16:48:31.739828 GOT SHARE! cccccc 3231a5e2 prev 08075e20 age 34.50s DEAD ON ARRIVAL
17:11:56.867175 GOT SHARE! cccccc fd25a9bd prev 69d47462 age 26.91s DEAD ON ARRIVAL
17:26:35.194804 GOT SHARE! cccccc 640e9ebd prev 5c2e2221 age 11.85s
17:35:39.829151 GOT SHARE! cccccc 582b0db9 prev f452f2f8 age 16.75s
17:41:35.629520 GOT SHARE! cccccc bd41d585 prev 32818a48 age 33.79s DEAD ON ARRIVAL
17:48:58.909271 GOT SHARE! cccccc ee2d6b93 prev 47bb9cfa age 9.51s
19:13:12.722993 GOT SHARE! cccccc 8ef4140e prev a402ee4a age 11.58s DEAD ON ARRIVAL
19:13:50.677687 GOT SHARE! cccccc f09c4eab prev d0613a01 age 28.44s DEAD ON ARRIVAL
19:15:47.942192 GOT SHARE! cccccc f81a2d80 prev 59599851 age 16.00s DEAD ON ARRIVAL

something is wrong, isn't it?  most are dead, and what does that "age" field really mean?

I'm using latest cgminer 2.2.1 on my miner, with I 7 (intensity) and just p2pool, I have a failover pool, to be honest, but with

Code:

"failover-only" : true

inside cgminer.conf.

Any idea?

best regards.

spiccioli.

Your dead share rates seems rather excessive, I haven't had any dead shares myself for two weeks almost (I've only got fairly slow miner though).
I've had bad experience with mixing traditional pool and p2pool with cgminer. Not sure what the logic behind it is, but in my case it ended up using long polling connection to traditional pool while doing work for p2pool. Since the polling cycle on p2pool is a lot faster than normal pools this leads to (possibly very) high stale/dead shares.
Normally you will see 'LONGPOLL requested work restart..' every couple of seconds with p2pool. If you're not seeing that, it might be this long polling issue. I'd try with just one pool configured.
Second thing I'd look at is if the host running your p2pool daemon is not too overloaded.

[thirdlight]

spiccioli, try cgminer with only 1 thread, it's

Code:

"gpu-threads": "1"

in the config file.

Let us know if it makes a difference.

[spiccioli]

Any idea?

What version of p2pool are you running? That looks like miner output. What does your p2pool output look like?

As has been said many times, stales in p2pool are higher than a traditional pool

Red Emerald,

that is p2pool (I'm using latest) log file filtered for "GOT SHARE" lines.

I uderstad higher, but here they're mostly dead and it seems other people on p2pool have a few dead shares even with thousands good ones received.

Look, I've just restarted p2pool

Code:

08:59:19.034126 Average time between blocks: 0.40 days
08:59:19.034604 Pool stales: 10% Own: 67±33% Own efficiency: 37±37%
08:59:20.354290 New work for worker! Difficulty: 331.665349 Payout if block: 0.046013 BTC Total block value: 50.001500 BTC including 21 transactions
08:59:22.043901 Pool: 162GH/s in 17341 shares (17345/17345 verified) Recent: 0.13% >217MH/s Shares: 2 (0 orphan, 2 dead) Peers: 10
08:59:22.044154 Average time between blocks: 0.40 days
08:59:22.044419 Pool stales: 10% Own: 67±33% Own efficiency: 37±37%

and I already have 2 deads.

spiccioli.

[spiccioli]

spiccioli, try cgminer with only 1 thread, it's

Code:

"gpu-threads": "1"

in the config file.

Let us know if it makes a difference.

thirdlight,

with latest cgminer (2.2.1) using dynamic intensity forces a single therad per GPU, so I've set it to dynamic right now, let's see what happens.

regards.

spiccioli.

[spiccioli]

Normally you will see 'LONGPOLL requested work restart..' every couple of seconds with p2pool. If you're not seeing that, it might be this long polling issue. I'd try with just one pool configured.

Second thing I'd look at is if the host running your p2pool daemon is not too overloaded.

eja,

I see them and, no, the host with p2pool is a 3GhZ PentiumD/HT pc with xubuntu running just p2pool and bitcoind.

regards.

spiccioli.

[waspoza]

Does really pool hash rate dropped that much or its only me?

[Qoheleth]

Does really pool hash rate dropped that much or its only me?

I'm seeing 153GH/s total network power on my client

[waspoza]

Yea looks like my client is bugged. Pool hashrate went to zero, local hashrate is good. Strange.

[forrestv]

Yea looks like my client is bugged. Pool hashrate went to zero, local hashrate is good. Strange.

Have you upgraded to the latest version? There was a problem that caused this that was fixed two weeks ago.

[Gabi]

175ghash/s now, good job guys!

[waspoza]

Yea looks like my client is bugged. Pool hashrate went to zero, local hashrate is good. Strange.

Have you upgraded to the latest version? There was a problem that caused this that was fixed two weeks ago.

Ok, pulled newest version from git, and looks good now. Thanks.

[wachtwoord]

Okay these are the result for running today for 11 hours at 251 Mhash

My miner reports: [251.34 Mhash/sec] [249 Accepted] [1 Rejected] [RPC (+LP)]

p2pool reports:

2012-02-02 18:55:01.238000 Pool: 157GH/s in 17350 shares (17354/17354 verified)
Recent: 0.13% >203MH/s Shares: 6 (0 orphan, 0 dead) Peers: 10 (0 incoming)
2012-02-02 18:55:01.238000 Average time between blocks: 0.41 days
2012-02-02 18:55:01.238000 Pool stales: 9% Own: 20±20% Own efficiency: 88±21%

This seems rather contradictionary to me:

Miner reports: 0.4%  stales (1 in 250)
p2pool reports 0% stales (0 in 6)
p2pool reports 20±20% (where does this number come from)

Also, why does it recognize only 6 of 249 submitted shares?

Can someone explain all this to me?

Haven't received a payout for two days. Is this just another block drought or is something wrong with my setup?
I'm seeing 156GH/s so I'm not on the split chain.

Since the transactions count as mined, you need 120 confirms for them to show up -- could that be why you're not seeing them?

Thanks for that explanation. Anyone for the other questions I posted?  I had similar results today (5 shares, 0orphan 0 dead but 22±22% own stales reported)

[ThiagoCMC]

I'll try P2Pool for Bitcoin and Litecoin at the same machine but:

> Last, forward port 9333 through your firewall to the host running p2pool! (Oh, and join #p2pool on freenode!)

Litecoin already listen @ 9333... So as P2Pool...

What is the best workaround?!

Move litecoin to 10333 or P2Pool to 10333, for example?!

[dishwara]

I don't know from where i got this, so i ask here.

Is p2pool is the pool that supports merged mining of bitcoins, namecoins & litecoins?

[ThiagoCMC]

I don't know from where i got this, so i ask here.

Is p2pool is the pool that supports merged mining of bitcoins, namecoins & litecoins?

Kind of... But...

1- One P2Pool instance for Bitcoin and Namecoin (probably on port 9333) but, Bitcoin @ P2Pool and Namecoin local solo;
2- Another P2Pool instance for Litecoin.

What needs to be done is: implement real P2Pool for Namecoin...

Best!
Thiago

[Syke]

I'll try P2Pool for Bitcoin and Litecoin at the same machine but:

> Last, forward port 9333 through your firewall to the host running p2pool! (Oh, and join #p2pool on freenode!)

Litecoin already listen @ 9333... So as P2Pool...

What is the best workaround?!

Move litecoin to 10333 or P2Pool to 10333, for example?!

Yes. It doesn't matter which one you move. I already had p2pool running so I added:

rpcport=9334
port=9335

to litecoin.conf.

[cheat_2_win]

For people like me who are beginning with p2pool:

When p2pool is started for the first time, it might look like it is not doing anything. Go to data/bitcoin folder inside the p2pool directory. There are shareX files. If the sizes of all of those files do not change, then p2pool is stuck. Otherwise, it is downloading shares from its peers. Be patient, once the download is complete, mining can continue.

It was very confusing for me at the beginning and I was not able to find any means to check whether shares are being downloaded or p2pool is stuck.. Noone mentioned anything about the shareX files in the forum as well.

[Raize]

I started using P2Pool earlier this week.

IMHO, the best thing P2Pool could do is operate in a manner similar to CGMiner or these other programs that keep a running tally of "shares" or accept/rejects or hash or something.

I know my CGMiner is working because I can look at it and see my hash rate totals on all my video cards. I can visually see it working. It calculates total hash rate and records accepts for me. If P2Pool had a way to calculate how many total hash was being thrown through it, miners would have less of an incentive to keep mining at regular pools. Right now I have to read the forums to understand what is going on.