Bitcoin Forum
December 08, 2016, 12:33:38 AM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 [112] 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 ... 744 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2032585 times)
Smoovious
Hero Member
*****
Offline Offline

Activity: 504

Scattering my bits around the net since 1980


View Profile
May 08, 2012, 12:13:59 AM
 #2221

Also have to keep in mind, that blocks and shares don't propogate instantly, being a decentralized network.

When one of us finds a block, it is relayed to the network more like ripples on a pond. Your P2P tells at least 10 friends, and their P2P's tell at least 10 friends, and so on and so on. Depending on how many nodes there are, it could take a long time (relatively speaking) for every node to get the new block.

If another node also solves a block before the first block's ripple reaches it, it sends out its own ripples, and eventually those ripples meet and try and cancel each other out, like the earlier poster saw with it going back and forth, until the stronger ripple has dissapated the weaker ripple, resulting in the orphan.

-- Smoov
1481157218
Hero Member
*
Offline Offline

Posts: 1481157218

View Profile Personal Message (Offline)

Ignore
1481157218
Reply with quote  #2

1481157218
Report to moderator
1481157218
Hero Member
*
Offline Offline

Posts: 1481157218

View Profile Personal Message (Offline)

Ignore
1481157218
Reply with quote  #2

1481157218
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481157218
Hero Member
*
Offline Offline

Posts: 1481157218

View Profile Personal Message (Offline)

Ignore
1481157218
Reply with quote  #2

1481157218
Report to moderator
Tittiez
Hero Member
*****
Offline Offline

Activity: 686



View Profile
May 08, 2012, 12:49:04 AM
 #2222

NOBODY SAY ANYTHING ABOUT THE L WORD
iopq
Hero Member
*****
Offline Offline

Activity: 644


View Profile
May 08, 2012, 01:51:08 AM
 #2223

NOBODY SAY ANYTHING ABOUT THE L WORD
First rule of p2pool: you do not talk about luck
Second rule of p2pool: you DO NOT talk about luck

ChanceCoats123
Hero Member
*****
Offline Offline

Activity: 680



View Profile
May 08, 2012, 02:09:17 AM
 #2224

NOBODY SAY ANYTHING ABOUT THE L WORD
First rule of p2pool: you do not talk about luck
Second rule of p2pool: you DO NOT talk about luck

Such a great movie.
Aseras
Hero Member
*****
Offline Offline

Activity: 658


View Profile
May 08, 2012, 03:16:12 PM
 #2225

Good job cabin. Screw us all.

https://bitcointalk.org/index.php?topic=18313.msg886892#msg886892
Smoovious
Hero Member
*****
Offline Offline

Activity: 504

Scattering my bits around the net since 1980


View Profile
May 08, 2012, 03:25:05 PM
 #2226

Alright, I can bring the noose and a chair, but someone is gonna have to bring the tree...

-- Smoov
Tittiez
Hero Member
*****
Offline Offline

Activity: 686



View Profile
May 09, 2012, 02:43:00 AM
 #2227

Alright, I can bring the noose and a chair, but someone is gonna have to bring the tree...

-- Smoov

Leaching off your Litecoin P2Pool node, thanks!
bitpop
Legendary
*
Offline Offline

Activity: 1932


https://keybase.io/bitpop


View Profile WWW
May 09, 2012, 02:44:50 AM
 #2228

Lynching off your Litecoin P2Pool node, thanks!

Reputation  |  PGP  |  DigitalOcean  |  OpenVPN 2GB Free  |  TorGuard  |  Ethereum Classic
Bitcoin: 3DSh6AnmvBpDJFUz2mnLirMLmTMcFs9nDm
Bitmessage: BM-2cXN9j8NFT2n1FxDVQ6HQq4D4MZuuaBFyb
Smoovious
Hero Member
*****
Offline Offline

Activity: 504

Scattering my bits around the net since 1980


View Profile
May 09, 2012, 11:31:17 AM
 #2229

Leaching off your Litecoin P2Pool node, thanks!
Oh! hey, cool! Smiley

Thanks, the more the merrier XD

-- Smoov
vindimy
Full Member
***
Offline Offline

Activity: 239



View Profile
May 09, 2012, 06:27:00 PM
 #2230

Guys,

I've just upgraded to 0.11.1 (did a git clone) after seeing the warning messages (like below). However, the warnings didn't go away after I restarted. Is that normal?

Code:
2012-05-09 18:28:18.833633  Pool: 357GH/s Stale rate: 10.9% Expected time to block: 5.8 hours
2012-05-09 18:28:21.877741 > ########################################
2012-05-09 18:28:21.877929 > >>> WARNING: A MAJORITY OF SHARES CONTAIN A VOTE FOR AN UNSUPPORTED SHARE IMPLEMENTATION! (v2 with 86% support)
2012-05-09 18:28:21.877989 > >>> An upgrade is likely necessary. Check http://p2pool.forre.st/ for more information.
2012-05-09 18:28:21.878055 > ########################################
2012-05-09 18:28:21.878105 P2Pool: 19106 shares in chain (19110 verified/19110 total) Peers: 11 (0 incoming)
2012-05-09 18:28:21.878146  Local: 1380MH/s in last 3.4 minutes Local dead on arrival: ~6.1% (2-15%) Expected time to share: 41.8 minutes
2012-05-09 18:28:21.878186  Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0970 BTC
2012-05-09 18:28:21.878231  Pool: 357GH/s Stale rate: 10.9% Expected time to block: 5.8 hours
2012-05-09 18:28:24.924752 > ########################################
2012-05-09 18:28:24.924897 > >>> WARNING: A MAJORITY OF SHARES CONTAIN A VOTE FOR AN UNSUPPORTED SHARE IMPLEMENTATION! (v2 with 86% support)
2012-05-09 18:28:24.924956 > >>> An upgrade is likely necessary. Check http://p2pool.forre.st/ for more information.
2012-05-09 18:28:24.925011 > ########################################
2012-05-09 18:28:24.925247 P2Pool: 19106 shares in chain (19110 verified/19110 total) Peers: 11 (0 incoming)
2012-05-09 18:28:24.925360  Local: 1401MH/s in last 3.5 minutes Local dead on arrival: ~5.9% (2-15%) Expected time to share: 41.1 minutes
2012-05-09 18:28:24.925405  Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0970 BTC
2012-05-09 18:28:24.925453  Pool: 357GH/s Stale rate: 10.9% Expected time to block: 5.8 hours
2012-05-09 18:28:25.560529 New work for worker! Difficulty: 0.999985 Share difficulty: 811.979872 Total block value: 50.276000 BTC including 190 transactions
2012-05-09 18:28:25.583851 New work for worker! Difficulty: 0.999985 Share difficulty: 811.979872 Total block value: 50.276000 BTC including 190 transactions
2012-05-09 18:28:25.608886 New work for worker! Difficulty: 1.000000 Share difficulty: 811.979872 Total block value: 50.276000 BTC including 190 transactions
2012-05-09 18:28:27.969760 > ########################################
2012-05-09 18:28:27.969910 > >>> WARNING: A MAJORITY OF SHARES CONTAIN A VOTE FOR AN UNSUPPORTED SHARE IMPLEMENTATION! (v2 with 86% support)
2012-05-09 18:28:27.969977 > >>> An upgrade is likely necessary. Check http://p2pool.forre.st/ for more information.
2012-05-09 18:28:27.970057 > ########################################
2012-05-09 18:28:27.970107 P2Pool: 19107 shares in chain (19111 verified/19111 total) Peers: 11 (0 incoming)
2012-05-09 18:28:27.970146  Local: 1401MH/s in last 3.5 minutes Local dead on arrival: ~7.2% (3-16%) Expected time to share: 41.1 minutes
2012-05-09 18:28:27.970185  Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0970 BTC
2012-05-09 18:28:27.970229  Pool: 357GH/s Stale rate: 10.9% Expected time to block: 5.8 hours
2012-05-09 18:28:31.016919 > ########################################
2012-05-09 18:28:31.017079 > >>> WARNING: A MAJORITY OF SHARES CONTAIN A VOTE FOR AN UNSUPPORTED SHARE IMPLEMENTATION! (v2 with 86% support)
2012-05-09 18:28:31.017137 > >>> An upgrade is likely necessary. Check http://p2pool.forre.st/ for more information.
2012-05-09 18:28:31.017192 > ########################################
2012-05-09 18:28:31.017240 P2Pool: 19107 shares in chain (19111 verified/19111 total) Peers: 11 (0 incoming)
2012-05-09 18:28:31.017279  Local: 1421MH/s in last 3.6 minutes Local dead on arrival: ~7.0% (3-16%) Expected time to share: 40.6 minutes
2012-05-09 18:28:31.017319  Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0970 BTC
2012-05-09 18:28:31.017363  Pool: 357GH/s Stale rate: 10.9% Expected time to block: 5.8 hours
2012-05-09 18:28:34.061658 > ########################################
2012-05-09 18:28:34.061830 > >>> WARNING: A MAJORITY OF SHARES CONTAIN A VOTE FOR AN UNSUPPORTED SHARE IMPLEMENTATION! (v2 with 86% support)
2012-05-09 18:28:34.061922 > >>> An upgrade is likely necessary. Check http://p2pool.forre.st/ for more information.


I am 100% sure that I'm not running an older version. My OS is latest 64-bit Debian.

forrestv
Hero Member
*****
Offline Offline

Activity: 510


View Profile
May 09, 2012, 06:37:18 PM
 #2231

vindimy, what does run_p2pool.py --version print?

1J1zegkNSbwX4smvTdoHSanUfwvXFeuV23
P4man
Hero Member
*****
Offline Offline

Activity: 504



View Profile
May 09, 2012, 06:48:07 PM
 #2232

I got a question; is there a way to determine if a pool+worker combo is a p2pool worker using cgminer (api) or some other way?

IOW, if I give you an IP+port, workername and password, could you tell if its p2pool or a regular pool?

twmz
Hero Member
*****
Offline Offline

Activity: 737



View Profile
May 09, 2012, 07:42:32 PM
 #2233

I got a question; is there a way to determine if a pool+worker combo is a p2pool worker using cgminer (api) or some other way?

IOW, if I give you an IP+port, workername and password, could you tell if its p2pool or a regular pool?

Without connecting to it?  I might guess it was p2pool if the port was 9332 since that is not commonly used for other bitcoin pools.

If I can connect to it, then p2pool includes a "X-Is-P2Pool: true" HTTP header in its response to a getwork request.

Was I helpful?  1TwmzX1wBxNF2qtAJRhdKmi2WyLZ5VHRs
WoT, GPG

Bitrated user: ewal.
vindimy
Full Member
***
Offline Offline

Activity: 239



View Profile
May 09, 2012, 09:53:34 PM
 #2234

vindimy, what does run_p2pool.py --version print?

Code:
dv@lax1:/opt/p2$ python run_p2pool.py --version
/opt/p2pool/forrestv-p2pool-eb0b203/p2pool/util/pack.py:187: DeprecationWarning: object.__new__() takes no parameters
  return Type.__new__(cls, bits, endianness)
eb0b203

dv@lax1:/opt/p2$ python --version
Python 2.6.6

dv@lax1:/opt/p2pool$ ll
total 680
-rw-r--r-- 1 dv   dv   352751 Mar 24 01:13 forrestv-p2pool-0.10.3-0-g71ef0aa.tar.gz
-rw-r--r-- 1 root root 318393 May  9 18:16 forrestv-p2pool-0.11.1-0-gd514a6c.tar.gz
drwxrwxr-x 8 root root   4096 May  3 07:28 forrestv-p2pool-04283e9/
drwxr-xr-x 9 dv   dv     4096 Mar 24 01:19 forrestv-p2pool-eb0b203/

Now I see that it's still running old version of p2pool. And I know why. I updates my symlink to point to new installation, but I didn't chdir out-and-in of the symlinked dir. After doing that I get:

Code:
dv@lax1:/opt/p2$ python run_p2pool.py --version
/opt/p2pool/git/p2pool/p2pool/util/pack.py:186: DeprecationWarning: object.__new__() takes no parameters
  return Type.__new__(cls, bits, endianness)
0.11.1-27-g245da11

All is well now. Thanks forrestv! Coins going your way.

EDIT:

When I started cgminer again, I got this exception. Not sure if important.
Code:
2012-05-09 21:58:32.480639
2012-05-09 21:58:38.464645
2012-05-09 21:58:38.464793 GOT BLOCK FROM PEER! Passing to bitcoind! 6be723ad bitcoin: http://blockexplorer.com/block/000000000000084045d435e306638d746ecd67438a6426e15c4aca0b6be723ad
2012-05-09 21:58:38.464845
2012-05-09 21:58:57.475813 Requesting parent share 84b554c3 from 72.14.191.28:9333
2012-05-09 21:58:57.476478 ... done processing 1001 shares. New: 1001 Have: 12028/~17280
2012-05-09 21:58:57.476928 > Watchdog timer went off at:
2012-05-09 21:58:57.476987 >   File "run_p2pool.py", line 5, in <module>
2012-05-09 21:58:57.477032 >     main.run()
2012-05-09 21:58:57.477077 >   File "/opt/p2pool/git/p2pool/p2pool/main.py", line 1073, in run
2012-05-09 21:58:57.477119 >     reactor.run()
2012-05-09 21:58:57.477160 >   File "/usr/lib/python2.6/dist-packages/twisted/internet/base.py", line 1165, in run
2012-05-09 21:58:57.477205 >     self.mainLoop()
2012-05-09 21:58:57.477246 >   File "/usr/lib/python2.6/dist-packages/twisted/internet/base.py", line 1177, in mainLoop
2012-05-09 21:58:57.477289 >     self.doIteration(t)
2012-05-09 21:58:57.477331 >   File "/usr/lib/python2.6/dist-packages/twisted/internet/selectreactor.py", line 140, in doSelect
2012-05-09 21:58:57.477374 >     _logrun(selectable, _drdw, selectable, method, dict)
2012-05-09 21:58:57.477638 >   File "/usr/lib/python2.6/dist-packages/twisted/python/log.py", line 84, in callWithLogger
2012-05-09 21:58:57.477748 >     return callWithContext({"system": lp}, func, *args, **kw)
2012-05-09 21:58:57.477794 >   File "/usr/lib/python2.6/dist-packages/twisted/python/log.py", line 69, in callWithContext
2012-05-09 21:58:57.477838 >     return context.call({ILogContext: newCtx}, func, *args, **kw)
2012-05-09 21:58:57.477880 >   File "/usr/lib/python2.6/dist-packages/twisted/python/context.py", line 59, in callWithContext
2012-05-09 21:58:57.477923 >     return self.currentContext().callWithContext(ctx, func, *args, **kw)
2012-05-09 21:58:57.477964 >   File "/usr/lib/python2.6/dist-packages/twisted/python/context.py", line 37, in callWithContext
2012-05-09 21:58:57.478006 >     return func(*args,**kw)
2012-05-09 21:58:57.478230 >   File "/usr/lib/python2.6/dist-packages/twisted/internet/selectreactor.py", line 146, in _doReadOrWrite
2012-05-09 21:58:57.478321 >     why = getattr(selectable, method)()
2012-05-09 21:58:57.478367 >   File "/usr/lib/python2.6/dist-packages/twisted/internet/tcp.py", line 460, in doRead
2012-05-09 21:58:57.478413 >     return self.protocol.dataReceived(data)
2012-05-09 21:58:57.478456 >   File "/opt/p2pool/git/p2pool/p2pool/p2p.py", line 57, in new_dataReceived
2012-05-09 21:58:57.478499 >     old_dataReceived(data)
2012-05-09 21:58:57.478539 >   File "/opt/p2pool/git/p2pool/p2pool/util/datachunker.py", line 40, in _DataChunker
2012-05-09 21:58:57.478581 >     wants = receiver.send(buf.get(wants))
2012-05-09 21:58:57.478625 >   File "/opt/p2pool/git/p2pool/p2pool/util/p2protocol.py", line 48, in dataReceiver
2012-05-09 21:58:57.478668 >     self.packetReceived(command, type_.unpack(payload))
2012-05-09 21:58:57.478710 >   File "/opt/p2pool/git/p2pool/p2pool/p2p.py", line 69, in packetReceived
2012-05-09 21:58:57.478752 >     p2protocol.Protocol.packetReceived(self, command, payload2)
2012-05-09 21:58:57.478794 >   File "/opt/p2pool/git/p2pool/p2pool/util/p2protocol.py", line 61, in packetReceived
2012-05-09 21:58:57.478836 >     handler(**payload2)
2012-05-09 21:58:57.478876 >   File "/opt/p2pool/git/p2pool/p2pool/p2p.py", line 205, in handle_shares
2012-05-09 21:58:57.478919 >     self.node.handle_shares([p2pool_data.load_share(share, self.node.net, self) for share in shares], self)
2012-05-09 21:58:57.478962 >   File "/opt/p2pool/git/p2pool/p2pool/main.py", line 265, in handle_shares
2012-05-09 21:58:57.479004 >     set_real_work2()
2012-05-09 21:58:57.479044 >   File "/opt/p2pool/git/p2pool/p2pool/main.py", line 183, in set_real_work2
2012-05-09 21:58:57.479086 >     best, desired = tracker.think(get_height_rel_highest, pre_current_work.value['previous_block'], pre_current_work.value['bits'])
2012-05-09 21:58:57.479165 >   File "/opt/p2pool/git/p2pool/p2pool/data.py", line 403, in think
2012-05-09 21:58:57.479208 >     if not self.attempt_verify(share):
2012-05-09 21:58:57.479250 >   File "/opt/p2pool/git/p2pool/p2pool/data.py", line 353, in attempt_verify
2012-05-09 21:58:57.479291 >     share.check(self)
2012-05-09 21:58:57.479331 >   File "/opt/p2pool/git/p2pool/p2pool/data.py", line 248, in check
2012-05-09 21:58:57.479374 >     share_info, gentx = self.generate_transaction(tracker, self.share_info['share_data'], self.header['bits'].target, self.share_info['timestamp'], self.share_info['bits'].target, self.common['ref_merkle_link'], self.net)
2012-05-09 21:58:57.479424 >   File "/opt/p2pool/git/p2pool/p2pool/data.py", line 134, in generate_transaction
2012-05-09 21:58:57.479466 >     65535*net.SPREAD*bitcoin_data.target_to_average_attempts(block_target),
2012-05-09 21:58:57.479507 >   File "/opt/p2pool/git/p2pool/p2pool/util/skiplist.py", line 55, in __call__
2012-05-09 21:58:57.479550 >     updates[x] = updates[x][0], self.combine_deltas(updates[x][1], delta) if updates[x][1] is not None else delta
2012-05-09 21:58:57.479594 >   File "/opt/p2pool/git/p2pool/p2pool/data.py", line 303, in combine_deltas
2012-05-09 21:58:57.479636 >     return share_count1 + share_count2, math.add_dicts(weights1, weights2), total_weight1 + total_weight2, total_donation_weight1 + total_donation_weight2
2012-05-09 21:58:57.479680 >   File "/opt/p2pool/git/p2pool/p2pool/util/math.py", line 69, in add_dicts
2012-05-09 21:58:57.479721 >     return dict((k, v) for k, v in res.iteritems() if v != zero)
2012-05-09 21:58:57.479762 >   File "/opt/p2pool/git/p2pool/p2pool/util/math.py", line 69, in <genexpr>
2012-05-09 21:58:57.479803 >     return dict((k, v) for k, v in res.iteritems() if v != zero)
2012-05-09 21:58:57.479844 >   File "/opt/p2pool/git/p2pool/p2pool/main.py", line 740, in <lambda>
2012-05-09 21:58:57.479886 >     sys.stderr.write, 'Watchdog timer went off at:\n' + ''.join(traceback.format_stack())
2012-05-09 21:58:57.505188 P2Pool: 12027 shares in chain (3387 verified/12028 total) Peers: 6 (0 incoming)
2012-05-09 21:58:57.505292  Local: 728MH/s in last 58.9 seconds Local dead on arrival: ~100.0% (72-100%) Expected time to share: 1.2 hours

Frizz23
Hero Member
*****
Offline Offline

Activity: 658



View Profile
May 10, 2012, 09:32:18 AM
 #2235

How can I verify that merged mining is working for me?

I haven't found a single NMC block since I use p2pool (since January).

kano
Legendary
*
Offline Offline

Activity: 1932


Linux since 1997 RedHat 4


View Profile
May 10, 2012, 10:49:00 AM
 #2236

How can I verify that merged mining is working for me?

I haven't found a single NMC block since I use p2pool (since January).

One way to know: If you find a BTC block then you should also find an NMC block Smiley
NMC blocks are expected to be more often, but certainly not less often than a BTC block
There are conditions where that wouldn't be true, but those conditions are not likely to ever happen.

Pool: https://kano.is BTC: 1KanoiBupPiZfkwqB7rfLXAzPnoTshAVmb
CKPool and CGMiner developer, IRC FreeNode #ckpool and #cgminer kanoi
Help keep Bitcoin secure by mining on pools with Stratum, the best protocol to mine Bitcoins with ASIC hardware
Smoovious
Hero Member
*****
Offline Offline

Activity: 504

Scattering my bits around the net since 1980


View Profile
May 10, 2012, 11:35:08 AM
 #2237

How can I verify that merged mining is working for me?

I haven't found a single NMC block since I use p2pool (since January).

One way to know: If you find a BTC block then you should also find an NMC block Smiley
NMC blocks are expected to be more often, but certainly not less often than a BTC block
There are conditions where that wouldn't be true, but those conditions are not likely to ever happen.
...but it has to be you finding the BTC block, not the pool.

Try adding this to your namecoin.conf file: printtoconsole=1

Then you should be able to see P2Pool polling namecoind. Also, if P2Pool wasn't able to communicate with namecoind, you'd see a lot of error messages on the P2Pool end.

I don't know if namecoin has a testnet set up, but try switching to that for a little while too. It might have a much lower difficulty to test with.

-- Smoov
Isokivi
Hero Member
*****
Offline Offline

Activity: 924


Items flashing here available at btctrinkets.com


View Profile WWW
May 10, 2012, 01:33:38 PM
 #2238

Is there any way to identify which rig, or even better which gpu is responsible for my orphans/stales ?

Bitcoin trinkets now on my online store: btc trinkets.com <- Bitcoin Tiepins, cufflinks, lapel pins, keychains, card holders and challenge coins.
twmz
Hero Member
*****
Offline Offline

Activity: 737



View Profile
May 10, 2012, 01:37:14 PM
 #2239

Is there any way to identify which rig, or even better which gpu is responsible for my orphans/stales ?

Use a different username for each rig or gpu and then look at the graphs.  There will be a separate graph for each username and you can see individual stale statistics for each.

Was I helpful?  1TwmzX1wBxNF2qtAJRhdKmi2WyLZ5VHRs
WoT, GPG

Bitrated user: ewal.
DeathAndTaxes
Donator
Legendary
*
Offline Offline

Activity: 1218


Gerald Davis


View Profile
May 10, 2012, 01:51:03 PM
 #2240

Is there any way to identify which rig, or even better which gpu is responsible for my orphans/stales ?

Use a different username for each rig or gpu and then look at the graphs.  There will be a separate graph for each username and you can see individual stale statistics for each.

Good "p2pool pro-tip"!

That will only show DOA though.

Orphans (not to be confused with DOA) really aren't GPU/rig dependent.  All your rigs are sending shares to the p2pool instance.  If the p2pool instance finds the shares bad or old then it will be marked DOA.  If they aren't DOA they are all submitted to the network.  The orphan rate should be roughly the same for all GPUs/rigs.  Any rig/miner/GPU problems should show up in increased DOA rate and as twmz indicated using a seperate username for each rig can help spot that.

Also I would recommend ANUBIS (search the forum).  I nice web monitor to keep track of multiple GPU and multiple rigs by using the cgminer API.  Easy to spot a rig with above average rejects (DOAs) or communication problems (as well as overhot cards, or below avg hashrates).  If you want to do any per GPU analysis I recommend using static 1 diff shares locally.

Code:
user="username/A+B"

username is simply the identifier
/A is used to look for and submit higher diff shares (allows huge miners to helps smaller miners by taking on more variance)
+B is used to control the local share diff.

TL/DR
DOA = share is "bad" (it could be stale or it could just be invalid garbage) by the time YOUR p2pool node gets it.
Oprhan = your p2pool node saw the share as good but it lost the "race" w/ a competing share.
Stales = orphans + DOA.

Pages: « 1 ... 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 [112] 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 ... 744 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!