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

[forrestv]

Aseras/Subo1977: Are you using P2Pool 11.2 (the current newest version)? It fixed a memory leak that caused similar problems.

[Subo1977]

Aseras/Subo1977: Are you using P2Pool 11.2 (the current newest version)? It fixed a memory leak that caused similar problems.

Yes actual  p2pool and bitcoind from git

[Aseras]

Aseras/Subo1977: Are you using P2Pool 11.2 (the current newest version)? It fixed a memory leak that caused similar problems.

Yes 11.2 and .7.2

[Prattler]

Aseras/Subo1977: Are you using P2Pool 11.2 (the current newest version)? It fixed a memory leak that caused similar problems.

Perhaps issue a warning if twisted.version < 11.1? Because that could explain it...

[Subo1977]

Aseras/Subo1977: Are you using P2Pool 11.2 (the current newest version)? It fixed a memory leak that caused similar problems.

Perhaps issue a warning if twisted.version < 11.1? Because that could explain it...

at my side its Ubuntu 12.10 X64 with all patches and python 2.7

[Prattler]

at my side its Ubuntu 12.10 X64 with all patches and python 2.7

Please run

Code:

python
import twisted
print twisted.version

and report the output.

[Rogue Star]

Please run

Code:

python
import twisted
print twisted.version

and report the output.

Sounds pretty much like my setup and problems, so it should be

>>> print twisted.version
[twisted, version 12.2.0]

[Subo1977]

at my side its Ubuntu 12.10 X64 with all patches and python 2.7

Please run

Code:

python
import twisted
print twisted.version

and report the output.

>>> import twisted
>>> print twisted.version
[twisted, version 12.2.0]
>>>

[rav3n_pl]

Another lead to find memory eating routine: see my graph: http://rav3n.dtdns.net:9332/static/graphs.html?Day
From about 3PM my miner stuck and send invalid works. In same time memory usage was growing more and more and not get down when I restart miner and bad to mining.
Maybe there is something wrong on stratum/miner connections like it was in p2p connections?
My node eats now 420MB and still slowly rising.
After restart w/o shares after it re-download share chain it is about 100MB less.

[Subo1977]

Bo One here who Discuss about the l word?

[Aseras]

Bo One here who Discuss about the l word?

It's pretty obvious something is wrong. normal variance should not be so cyclical.

http://p2pool.info/luck/

[spiccioli]

Bo One here who Discuss about the l word?

It's pretty obvious something is wrong. normal variance should not be so cyclical.

http://p2pool.info/luck/

To be honest even this "something is broken" issue is very cyclical ...

That said:

- memory consumption seems to happen less when using stratum (I've been using it for two days now and memory is stable around 400 Mb)
- upload traffic and "peers sent a transaction already known" should be addressed, if possible.

spiccioli

[mdude77]

Bo One here who Discuss about the l word?

It's pretty obvious something is wrong. normal variance should not be so cyclical.

http://p2pool.info/luck/

To be honest even this "something is broken" issue is very cyclical ...

Very true.  It's still the worst cycle I've ever seen.  I said that before and organ proved it's been worse.  I've wonder if there still have been worse days.

M

[rav3n_pl]

Just cant wait for 10x 1h blocks that are commin

[zvs]

Bo One here who Discuss about the l word?

It's pretty obvious something is wrong. normal variance should not be so cyclical.

http://p2pool.info/luck/

I now agree w/ people that something is wrong, but I don't think it's the cyclical nature of the luck, it's the gradual downturn...

stratum is much slower than longpolling, when not mining to localhost

[eleuthria]

Bo One here who Discuss about the l word?

It's pretty obvious something is wrong. normal variance should not be so cyclical.

http://p2pool.info/luck/

I now agree w/ people that something is wrong, but I don't think it's the cyclical nature of the luck, it's the gradual downturn...

stratum is much slower than longpolling, when not mining to localhost

Stratum is not inherently slower than longpolling.  In a proper implementation the notification times between long polling and between Stratum are identical (or faster on Stratum since the remote server does less work and requires less burst bandwidth to forward them).

[Aseras]

Pool is dying now.. Lost 1/4 of the hashrate. Perhaps it'll come back if there's a good day. Although that would take a 4-7 block streak to bring luck just up to 100%PPS levels for 90 days.

[organofcorti]

Pool is dying now.. Lost 1/4 of the hashrate. Perhaps it'll come back if there's a good day. Although that would take a 4-7 block streak to bring luck just up to 100%PPS levels for 90 days.

I think it's strange that bad luck streaks at non-PPS pools freak miners out less than bad luck at p2Pool - a pool where a pool op cannot maliciously cause bad luck (lookin' at you, Bitclockers 2011 - early 2012).

[tiberiandusk]

I switched back to Eclipse for a while. I was getting too many stales because my getblock latency is so high. Seems to be the internet here and there's nothing I can do about it.

[taltamir]

Pool is dying now.. Lost 1/4 of the hashrate. Perhaps it'll come back if there's a good day. Although that would take a 4-7 block streak to bring luck just up to 100%PPS levels for 90 days.

I think it's strange that bad luck streaks at non-PPS pools freak miners out less than bad luck at p2Pool - a pool where a pool op cannot maliciously cause bad luck (lookin' at you, Bitclockers 2011 - early 2012).

I was under the understanding that hashrate has nothing to do with luck.
Successfully finding coins fluctuates and could be said to vary based on luck but hashrate is constant for a given hardware barring bugs.