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

Red Emerald

hero member

Activity: 742

Merit: 500

Quote from: btctalk on December 04, 2012, 01:59:18 PM

Quote from: Red Emerald on December 04, 2012, 01:47:57 PM

You can't merge mine bitcoin and litecoin. That doesn't work.

So how is it possible to have a mining pool that supports LTC and BTC mining? it should be, on different ports Undecided

Run p2pool twice with different settings.

You will have one pool for BTC and one pool for LTC. Not one pool with ports for both.

Aseras

hero member

Activity: 658

Merit: 500

you can "merge mine" bitcoins and tell it to submit to litecoin but litecoin will reject every block, probably one every few seconds, you are probably hammering the crap out of your computer trying that.

You have to mine one of the other, they are incompatible.

you run separate instances on different ports, and you can only mine on one or the other with the same worker.

You can have the same gpu or whatever split and mine half on litecoin and half btc, but since btc needs high hashrate and low mem speed, and litecoin needs low rate and high mem speed it's not really feasible.

btctalk

full member

Activity: 137

Merit: 112

Quote from: Red Emerald on December 04, 2012, 01:47:57 PM

You can't merge mine bitcoin and litecoin. That doesn't work.

So how is it possible to have a mining pool that supports LTC and BTC mining? it should be, on different ports Undecided

Red Emerald

hero member

Activity: 742

Merit: 500

Quote from: btctalk on December 04, 2012, 01:41:48 PM

on my setup everything seems to be going fine on the miner's end but local hash rate shows weird behaviour like sometimes its 0 and sometimes it's twice what it supposed to be...

Code:

Version: 9.3
Pool rate: 359GH/s (20% stale) Share difficulty: 643
Node uptime: 0.037 days Peers: 6 out, 0 in
Local rate: 21.5MH/s (0.0% DOA) Expected time to share: 35.7 hours
Shares: 0 total (0 orphaned, 0 dead) Efficiency: ???

I think it could be related to this, i get this once in a while in the output:

Code:

2012-12-04 13:39:12.779581 P2Pool: 17318 shares in chain (8906 verified/17322 total) Peers: 6 (0 incoming)
2012-12-04 13:39:12.779671 Local: 14316kH/s in last 10.0 minutes Local dead on arrival: ~0.0% (0-66%) Expected time to share: 2.2 days
2012-12-04 13:39:12.779709 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 BTC
2012-12-04 13:39:12.779749 Pool: 351GH/s Stale rate: 19.5% Expected time to block: 11.7 hours
2012-12-04 13:39:26.673891 New work for worker! Difficulty: 0.999985 Share difficulty: 644.631003 Total block value: 25.409100 BTC including 508 transactions
2012-12-04 13:39:27.805831 P2Pool: 17319 shares in chain (8907 verified/17323 total) Peers: 6 (0 incoming)
2012-12-04 13:39:27.805917 Local: 14316kH/s in last 10.0 minutes Local dead on arrival: ~0.0% (0-66%) Expected time to share: 2.2 days
2012-12-04 13:39:27.805954 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 BTC
2012-12-04 13:39:27.806018 Pool: 351GH/s Stale rate: 19.6% Expected time to block: 11.7 hours
2012-12-04 13:39:28.809477 > Traceback (most recent call last):
2012-12-04 13:39:28.809570 > File "/usr/lib/python2.6/dist-packages/twisted/internet/defer.py", line 371, in _runCallbacks
2012-12-04 13:39:28.809611 > self.result = callback(self.result, *args, **kw)
2012-12-04 13:39:28.809648 > File "/usr/lib/python2.6/dist-packages/twisted/internet/defer.py", line 879, in gotResult
2012-12-04 13:39:28.809685 > _inlineCallbacks(r, g, deferred)
2012-12-04 13:39:28.809720 > File "/usr/lib/python2.6/dist-packages/twisted/internet/defer.py", line 821, in _inlineCallbacks
2012-12-04 13:39:28.809758 > result = result.throwExceptionIntoGenerator(g)
2012-12-04 13:39:28.809794 > File "/usr/lib/python2.6/dist-packages/twisted/python/failure.py", line 338, in throwExceptionIntoGenerator
2012-12-04 13:39:28.809833 > return g.throw(self.type, self.value, self.tb)
2012-12-04 13:39:28.809868 > --- ---
2012-12-04 13:39:28.809902 > File "/home/shayan/Downloads/p2pool/p2pool/util/deferral.py", line 41, in f
2012-12-04 13:39:28.809938 > result = yield func(*args, **kwargs)
2012-12-04 13:39:28.809973 > File "/usr/lib/python2.6/dist-packages/twisted/internet/defer.py", line 821, in _inlineCallbacks
2012-12-04 13:39:28.810036 > result = result.throwExceptionIntoGenerator(g)
2012-12-04 13:39:28.810073 > File "/usr/lib/python2.6/dist-packages/twisted/python/failure.py", line 338, in throwExceptionIntoGenerator
2012-12-04 13:39:28.810109 > return g.throw(self.type, self.value, self.tb)
2012-12-04 13:39:28.810145 > File "/home/shayan/Downloads/p2pool/p2pool/util/jsonrpc.py", line 71, in callRemote
2012-12-04 13:39:28.810218 > raise Error_for_code(resp['error']['code'])(resp['error']['message'], resp['error'].get('data', None))
2012-12-04 13:39:28.810259 > p2pool.util.jsonrpc.NarrowError: -32601 Method not found
2012-12-04 13:39:37.247657 New work for worker! Difficulty: 0.999985 Share difficulty: 650.315749 Total block value: 25.411100 BTC including 510 transactions

could it be because I'm using merged minings with litecoin? litecoin pool is working fine, there's no problem with anything. just thought it could be related (no idea how Wink

)

You can't merge mine bitcoin and litecoin. That doesn't work.

btctalk

full member

Activity: 137

Merit: 112

on my setup everything seems to be going fine on the miner's end but local hash rate shows weird behaviour like sometimes its 0 and sometimes it's twice what it supposed to be...

Code:

Version: 9.3
Pool rate: 359GH/s (20% stale) Share difficulty: 643
Node uptime: 0.037 days Peers: 6 out, 0 in
Local rate: 21.5MH/s (0.0% DOA) Expected time to share: 35.7 hours
Shares: 0 total (0 orphaned, 0 dead) Efficiency: ???

I think it could be related to this, i get this once in a while in the output:

Code:

2012-12-04 13:39:12.779581 P2Pool: 17318 shares in chain (8906 verified/17322 total) Peers: 6 (0 incoming)
2012-12-04 13:39:12.779671 Local: 14316kH/s in last 10.0 minutes Local dead on arrival: ~0.0% (0-66%) Expected time to share: 2.2 days
2012-12-04 13:39:12.779709 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 BTC
2012-12-04 13:39:12.779749 Pool: 351GH/s Stale rate: 19.5% Expected time to block: 11.7 hours
2012-12-04 13:39:26.673891 New work for worker! Difficulty: 0.999985 Share difficulty: 644.631003 Total block value: 25.409100 BTC including 508 transactions
2012-12-04 13:39:27.805831 P2Pool: 17319 shares in chain (8907 verified/17323 total) Peers: 6 (0 incoming)
2012-12-04 13:39:27.805917 Local: 14316kH/s in last 10.0 minutes Local dead on arrival: ~0.0% (0-66%) Expected time to share: 2.2 days
2012-12-04 13:39:27.805954 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 BTC
2012-12-04 13:39:27.806018 Pool: 351GH/s Stale rate: 19.6% Expected time to block: 11.7 hours
2012-12-04 13:39:28.809477 > Traceback (most recent call last):
2012-12-04 13:39:28.809570 > File "/usr/lib/python2.6/dist-packages/twisted/internet/defer.py", line 371, in _runCallbacks
2012-12-04 13:39:28.809611 > self.result = callback(self.result, *args, **kw)
2012-12-04 13:39:28.809648 > File "/usr/lib/python2.6/dist-packages/twisted/internet/defer.py", line 879, in gotResult
2012-12-04 13:39:28.809685 > _inlineCallbacks(r, g, deferred)
2012-12-04 13:39:28.809720 > File "/usr/lib/python2.6/dist-packages/twisted/internet/defer.py", line 821, in _inlineCallbacks
2012-12-04 13:39:28.809758 > result = result.throwExceptionIntoGenerator(g)
2012-12-04 13:39:28.809794 > File "/usr/lib/python2.6/dist-packages/twisted/python/failure.py", line 338, in throwExceptionIntoGenerator
2012-12-04 13:39:28.809833 > return g.throw(self.type, self.value, self.tb)
2012-12-04 13:39:28.809868 > --- ---
2012-12-04 13:39:28.809902 > File "/home/shayan/Downloads/p2pool/p2pool/util/deferral.py", line 41, in f
2012-12-04 13:39:28.809938 > result = yield func(*args, **kwargs)
2012-12-04 13:39:28.809973 > File "/usr/lib/python2.6/dist-packages/twisted/internet/defer.py", line 821, in _inlineCallbacks
2012-12-04 13:39:28.810036 > result = result.throwExceptionIntoGenerator(g)
2012-12-04 13:39:28.810073 > File "/usr/lib/python2.6/dist-packages/twisted/python/failure.py", line 338, in throwExceptionIntoGenerator
2012-12-04 13:39:28.810109 > return g.throw(self.type, self.value, self.tb)
2012-12-04 13:39:28.810145 > File "/home/shayan/Downloads/p2pool/p2pool/util/jsonrpc.py", line 71, in callRemote
2012-12-04 13:39:28.810218 > raise Error_for_code(resp['error']['code'])(resp['error']['message'], resp['error'].get('data', None))
2012-12-04 13:39:28.810259 > p2pool.util.jsonrpc.NarrowError: -32601 Method not found
2012-12-04 13:39:37.247657 New work for worker! Difficulty: 0.999985 Share difficulty: 650.315749 Total block value: 25.411100 BTC including 510 transactions

could it be because I'm using merged minings with litecoin? litecoin pool is working fine, there's no problem with anything. just thought it could be related (no idea how Wink

)

Aseras

hero member

Activity: 658

Merit: 500

Quote from: aTg on December 04, 2012, 11:59:09 AM

Not solved by restarting the workers, only reaches the pool little more than 50% of my power. And if in the version 9.3.

Check bitcoind/qt process usage. If its over 40% drop the process priority to below normal.

aTg

legendary

Activity: 1358

Merit: 1000

Not solved by restarting the workers, only reaches the pool little more than 50% of my power. And if in the version 9.3.

Aseras

hero member

Activity: 658

Merit: 500

9.2 still gives me 100% orphan rate. 9.3 appears to be working ok, although 2 stales/doa right off the bat.

rav3n_pl

legendary

Activity: 1361

Merit: 1003

Don`t panic! Organize!

Quote from: aTg on December 03, 2012, 11:14:36 PM

Quote

Pool rate: 330GH/s (21% stale) Share difficulty: 577
Node uptime: 0.376 days Peers: 6 out, 1 in
Local rate: 39.1GH/s (62% DOA) Expected time to share: 0.0177 hours
Shares: 501 total (76 orphaned, 157 dead) Efficiency: 67.76%

I'm on version 9.3, which is going on?

Huge DOA rate indicates bad miner config or some issues/lags on connection.
See graphs on your node, maybe you see something.

Rogue Star

member

Activity: 89

Merit: 10

Quote from: aTg on December 03, 2012, 11:14:36 PM

Quote

Pool rate: 330GH/s (21% stale) Share difficulty: 577
Node uptime: 0.376 days Peers: 6 out, 1 in
Local rate: 39.1GH/s (62% DOA) Expected time to share: 0.0177 hours
Shares: 501 total (76 orphaned, 157 dead) Efficiency: 67.76%

I'm on version 9.3, which is going on?

Have you tried restarting your miner(s)? I find it helps to restart after an upgrade.

aTg

legendary

Activity: 1358

Merit: 1000

Quote

Pool rate: 330GH/s (21% stale) Share difficulty: 577
Node uptime: 0.376 days Peers: 6 out, 1 in
Local rate: 39.1GH/s (62% DOA) Expected time to share: 0.0177 hours
Shares: 501 total (76 orphaned, 157 dead) Efficiency: 67.76%

I'm on version 9.3, which is going on?

K1773R

legendary

Activity: 1792

Merit: 1008

/dev/null

@forrestv:
could you implement a way to print more details for such messages:

Code:

Merged block submittal result: True

something like this:

Quote

Merged block submittal for pool result: True

btharper

sr. member

Activity: 389

Merit: 250

Quote from: TAiS46 on December 03, 2012, 02:52:00 PM

but all other pools are working with bfl singles?

P2Pool generates a sharechain block every 10 seconds (on average) where the bitcoin blockchain only makes one block every 10 minutes (again, average).

The BFL single takes ~5 seconds to report back the work it computes.
On the full blockchain, or on work from pools this isn't a big deal since a share from five seconds ago is likely to be valid.
On P2Pool because of the lower block generation time a share from 5 seconds ago may or may not be valid, hence the high rejection rate (usually DOA iirc).

So to fix the problem BFL has to reprogram the singles to report back faster like GPUs or other FPGA units do, or P2Pool has to hardfork and use a longer time between blocks. Neither are particularly useful suggestions as changing P2pool for one manufacturer's mistakes is a lot of work for no reason, and a bad precedent; while getting BFL to update their firmware for an obsolete product is a waste of resources.

TAiS46

full member

Activity: 222

Merit: 100

but all other pools are working with bfl singles?

eleuthria

legendary

Activity: 1750

Merit: 1007

Quote from: TAiS46 on December 03, 2012, 02:48:11 PM

will there ever be a BFL single support?

You'd have to ask BFL that. They're the ones who made a poorly designed FPGA that doesn't report back solves until the nonce range is exhausted, and can't be interrupted while doing so.

TAiS46

full member

Activity: 222

Merit: 100

will there ever be a BFL single support?

PatMan

hero member

Activity: 924

Merit: 1000

Watch out for the "Neg-Rep-Dogie-Police".....

Quote from: rav3n_pl on December 03, 2012, 01:23:27 PM

Pull request sent... ;]

It would be nice if there were two different texts, one for each. It would defo help noobs like me out....lol

rav3n_pl

legendary

Activity: 1361

Merit: 1003

Don`t panic! Organize!

Pull request sent... ;]

PatMan

hero member

Activity: 924

Merit: 1000

Watch out for the "Neg-Rep-Dogie-Police".....

Quote from: rav3n_pl on December 03, 2012, 01:16:11 PM

Quote from: PatMan on December 03, 2012, 10:54:23 AM

Quote from: rav3n_pl on December 02, 2012, 05:46:59 PM

Pool wide DOA drop under 10%, looks like all troubles are gone.
Upgrade

I'm seeing a pool stale rate of 24% still.... Huh

Code:

Pool rate: 422GH/s (19% stale) Share difficulty: 740

but see hourly graphs:
DOA:7,5%
orphan: 12%
So sum will be 19%
I think this "stale" text should be changed to "DOA+orphan"

Yup, that would make sense.

rav3n_pl

legendary

Activity: 1361

Merit: 1003

Don`t panic! Organize!

Quote from: PatMan on December 03, 2012, 10:54:23 AM

Quote from: rav3n_pl on December 02, 2012, 05:46:59 PM

Pool wide DOA drop under 10%, looks like all troubles are gone.
Upgrade

I'm seeing a pool stale rate of 24% still.... Huh

Code:

Pool rate: 422GH/s (19% stale) Share difficulty: 740

but see hourly graphs:
DOA:7,5%
orphan: 12%
So sum will be 19%
I think this "stale" text should be changed to "DOA+orphan"

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