There's no way you could run bitcoind and p2pool on a Raspberry Pi and still expect to have a decent latency.
I might try this for my p2pool node with an eMMC NAND module for storage - http://www.hardkernel.com/renewal_2011/products/prdt_info.php
Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 522. (Read 2591920 times)
I might try this for my p2pool node with an eMMC NAND module for storage - http://www.hardkernel.com/renewal_2011/products/prdt_info.php
someone make a ready-to-run, easy-to-configure p2p-pool-node for raspberry.
put image on SD, insert, boot up, enter essential node stuff (.pdf format how-to supplied on d/l page), point miners - go!
There's no way you could run bitcoind and p2pool on a Raspberry Pi and still expect to have a decent latency.put image on SD, insert, boot up, enter essential node stuff (.pdf format how-to supplied on d/l page), point miners - go!
Indeed. 1GB RAM would be barely sufficient...
http://ask.gxsnmp.org:9332/static/
xxxxx@ask:~$ free
total used free shared buffers cached
Mem: 2061172 1970016 91156 0 53616 490908
-/+ buffers/cache: 1425492 635680
Swap: 1324028 104300 1219728
What's really interesting, is this is now a virtual machine as the previous hardware it was running on I needed for something else, and my latency went down and the efficiency went up. (go figure) However the virtual machine host is the same hardware specs as it's previous home (16 processor, 32 gigs mem, sas14k drives)
Here are the specs for the VM:
CPU -- Current Allocation 2
MEM -- Current Allocation 2048 MB
DISK -- VirtIO 30 GB.
NIC -- VirtIO -> br0 -> p1p1 (82571EB Gigabit Ethernet)
I'm not even gonna try and pretend I know wth that is all about
ok, seriously:
2013-06-25 19:07:09.184546 Punishing share for 'Block-stale detected! 6dd42c5d83567ac74ee79dd224864a71f2b6f1b0a9d28f7e6f < cd03f48c5345acfc88bcaff1f81f4fa125c18df73fdb6f792f'! Jumping from 062aec7c to
a3c6c045!
2013-06-25 19:07:09.187304 Punishing share for 'Block-stale detected! 6dd42c5d83567ac74ee79dd224864a71f2b6f1b0a9d28f7e6f < cd03f48c5345acfc88bcaff1f81f4fa125c18df73fdb6f792f'! Jumping from 062aec7c to
a3c6c045!
2013-06-25 19:07:09.950242 P2Pool: 17368 shares in chain (17373 verified/17373 total) Peers: 58 (4 incoming)
2013-06-25 19:07:09.950321 Local: 5970MH/s in last 10.0 minutes Local dead on arrival: ~3.9% (2-7%) Expected time to share: 12.7 minutes
2013-06-25 19:07:09.950354 Shares: 7 (1 orphan, 0 dead) Stale rate: ~14.3% (2-52%) Efficiency: ~100.5% (57-115%) Current payout: 0.2505 BTC
2013-06-25 19:07:09.950396 Pool: 552GH/s Stale rate: 14.7% Expected time to block: 1.7 days
2013-06-25 19:07:14.203573 Punishing share for 'Block-stale detected! 6dd42c5d83567ac74ee79dd224864a71f2b6f1b0a9d28f7e6f < cd03f48c5345acfc88bcaff1f81f4fa125c18df73fdb6f792f'! Jumping from 062aec7c to
a3c6c045!
2013-06-25 19:07:14.206408 Punishing share for 'Block-stale detected! 6dd42c5d83567ac74ee79dd224864a71f2b6f1b0a9d28f7e6f < cd03f48c5345acfc88bcaff1f81f4fa125c18df73fdb6f792f'! Jumping from 062aec7c to
a3c6c045!
2013-06-25 19:07:17.955598 P2Pool: 17368 shares in chain (17373 verified/17373 total) Peers: 58 (4 incoming)
2013-06-25 19:07:17.955675 Local: 6076MH/s in last 10.0 minutes Local dead on arrival: ~3.9% (2-7%) Expected time to share: 12.5 minutes
2013-06-25 19:07:17.955715 Shares: 7 (1 orphan, 0 dead) Stale rate: ~14.3% (2-52%) Efficiency: ~100.5% (57-115%) Current payout: 0.2505 BTC
2013-06-25 19:07:17.955759 Pool: 552GH/s Stale rate: 14.7% Expected time to block: 1.7 days
2013-06-25 19:07:19.184574 Punishing share for 'Block-stale detected! 6dd42c5d83567ac74ee79dd224864a71f2b6f1b0a9d28f7e6f < cd03f48c5345acfc88bcaff1f81f4fa125c18df73fdb6f792f'! Jumping from 062aec7c to
a3c6c045!
2013-06-25 19:07:19.187462 Punishing share for 'Block-stale detected! 6dd42c5d83567ac74ee79dd224864a71f2b6f1b0a9d28f7e6f < cd03f48c5345acfc88bcaff1f81f4fa125c18df73fdb6f792f'! Jumping from 062aec7c to
a3c6c045!
2013-06-25 19:07:21.728450 GOT SHARE! Drizztztzzztztzzzzztzz 1c29e828 prev a3c6c045 age 14.17s
2013-06-25 19:07:21.775027 New work for worker! Difficulty: 1.430048 Share difficulty: 1048.780971 Total block value: 25.000500 BTC including 1 transactions
2013-06-25 19:07:21.778033 New work for worker! Difficulty: 1.430048 Share difficulty: 1048.780971 Total block value: 25.000500 BTC including 1 transactions
2013-06-25 19:07:21.780870 New work for worker! Difficulty: 1.430048 Share difficulty: 1048.780971 Total block value: 25.000500 BTC including 1 transactions
2013-06-25 19:07:21.783816 New work for worker! Difficulty: 1.430048 Share difficulty: 1048.780971 Total block value: 25.000500 BTC including 1 transactions
2013-06-25 19:07:21.788586 New work for worker! Difficulty: 5.000000 Share difficulty: 1048.780971 Total block value: 25.000500 BTC including 1 transactions
2013-06-25 19:07:24.523397 Peer sent entire transaction c046b6219388a196710f6df1542ba8b2f8bc9e5ff8cd413644e141bb3a80b254 that was already received
2013-06-25 19:07:25.961603 P2Pool: 17347 shares in chain (17351 verified/17351 total) Peers: 58 (4 incoming)
2013-06-25 19:07:25.961688 Local: 6137MH/s in last 10.0 minutes Local dead on arrival: ~3.8% (2-7%) Expected time to share: 12.3 minutes
2013-06-25 19:07:25.961730 Shares: 8 (1 orphan, 0 dead) Stale rate: ~12.5% (2-48%) Efficiency: ~102.6% (62-115%) Current payout: 0.2532 BTC
2013-06-25 19:07:25.961757 Pool: 551GH/s Stale rate: 14.7% Expected time to block: 1.7 days
2013-06-25 19:07:27.725795 New work for worker! Difficulty: 1.401363 Share difficulty: 1039.385193 Total block value: 25.001500 BTC including 3 transactions
2013-06-25 19:07:27.728756 New work for worker! Difficulty: 1.401363 Share difficulty: 1039.385193 Total block value: 25.001500 BTC including 3 transactions
2013-06-25 19:07:27.731579 New work for worker! Difficulty: 1.401363 Share difficulty: 1039.385193 Total block value: 25.001500 BTC including 3 transactions
2013-06-25 19:07:27.734343 New work for worker! Difficulty: 1.401363 Share difficulty: 1039.385193 Total block value: 25.001500 BTC including 3 transactions
2013-06-25 19:07:27.737214 New work for worker! Difficulty: 5.000000 Share difficulty: 1039.385193 Total block value: 25.001500 BTC including 3 transactions
2013-06-25 19:07:32.898191 New work for worker! Difficulty: 1.432098 Share difficulty: 1043.302225 Total block value: 25.001500 BTC including 3 transactions
2013-06-25 19:07:32.901337 New work for worker! Difficulty: 1.432098 Share difficulty: 1043.302225 Total block value: 25.001500 BTC including 3 transactions
2013-06-25 19:07:32.906160 New work for worker! Difficulty: 1.432098 Share difficulty: 1043.302225 Total block value: 25.001500 BTC including 3 transactions
2013-06-25 19:07:32.909223 New work for worker! Difficulty: 1.432098 Share difficulty: 1043.302225 Total block value: 25.001500 BTC including 3 transactions
2013-06-25 19:07:32.912061 New work for worker! Difficulty: 5.000000 Share difficulty: 1043.302225 Total block value: 25.001500 BTC including 3 transactions
2013-06-25 19:07:33.963725 P2Pool: 17349 shares in chain (17353 verified/17353 total) Peers: 58 (4 incoming)
2013-06-25 19:07:33.963799 Local: 6126MH/s in last 10.0 minutes Local dead on arrival: ~3.9% (2-7%) Expected time to share: 12.1 minutes
2013-06-25 19:07:33.963832 Shares: 8 (2 orphan, 0 dead) Stale rate: ~25.0% (7-60%) Efficiency: ~88.3% (48-110%) Current payout: 0.2505 BTC
2013-06-25 19:07:33.963876 Pool: 553GH/s Stale rate: 15.1% Expected time to block: 1.7 days
is this a bug?
2013-06-25 19:07:09.184546 Punishing share for 'Block-stale detected! 6dd42c5d83567ac74ee79dd224864a71f2b6f1b0a9d28f7e6f < cd03f48c5345acfc88bcaff1f81f4fa125c18df73fdb6f792f'! Jumping from 062aec7c to
a3c6c045!
2013-06-25 19:07:09.187304 Punishing share for 'Block-stale detected! 6dd42c5d83567ac74ee79dd224864a71f2b6f1b0a9d28f7e6f < cd03f48c5345acfc88bcaff1f81f4fa125c18df73fdb6f792f'! Jumping from 062aec7c to
a3c6c045!
2013-06-25 19:07:09.950242 P2Pool: 17368 shares in chain (17373 verified/17373 total) Peers: 58 (4 incoming)
2013-06-25 19:07:09.950321 Local: 5970MH/s in last 10.0 minutes Local dead on arrival: ~3.9% (2-7%) Expected time to share: 12.7 minutes
2013-06-25 19:07:09.950354 Shares: 7 (1 orphan, 0 dead) Stale rate: ~14.3% (2-52%) Efficiency: ~100.5% (57-115%) Current payout: 0.2505 BTC
2013-06-25 19:07:09.950396 Pool: 552GH/s Stale rate: 14.7% Expected time to block: 1.7 days
2013-06-25 19:07:14.203573 Punishing share for 'Block-stale detected! 6dd42c5d83567ac74ee79dd224864a71f2b6f1b0a9d28f7e6f < cd03f48c5345acfc88bcaff1f81f4fa125c18df73fdb6f792f'! Jumping from 062aec7c to
a3c6c045!
2013-06-25 19:07:14.206408 Punishing share for 'Block-stale detected! 6dd42c5d83567ac74ee79dd224864a71f2b6f1b0a9d28f7e6f < cd03f48c5345acfc88bcaff1f81f4fa125c18df73fdb6f792f'! Jumping from 062aec7c to
a3c6c045!
2013-06-25 19:07:17.955598 P2Pool: 17368 shares in chain (17373 verified/17373 total) Peers: 58 (4 incoming)
2013-06-25 19:07:17.955675 Local: 6076MH/s in last 10.0 minutes Local dead on arrival: ~3.9% (2-7%) Expected time to share: 12.5 minutes
2013-06-25 19:07:17.955715 Shares: 7 (1 orphan, 0 dead) Stale rate: ~14.3% (2-52%) Efficiency: ~100.5% (57-115%) Current payout: 0.2505 BTC
2013-06-25 19:07:17.955759 Pool: 552GH/s Stale rate: 14.7% Expected time to block: 1.7 days
2013-06-25 19:07:19.184574 Punishing share for 'Block-stale detected! 6dd42c5d83567ac74ee79dd224864a71f2b6f1b0a9d28f7e6f < cd03f48c5345acfc88bcaff1f81f4fa125c18df73fdb6f792f'! Jumping from 062aec7c to
a3c6c045!
2013-06-25 19:07:19.187462 Punishing share for 'Block-stale detected! 6dd42c5d83567ac74ee79dd224864a71f2b6f1b0a9d28f7e6f < cd03f48c5345acfc88bcaff1f81f4fa125c18df73fdb6f792f'! Jumping from 062aec7c to
a3c6c045!
2013-06-25 19:07:21.728450 GOT SHARE! Drizztztzzztztzzzzztzz 1c29e828 prev a3c6c045 age 14.17s
2013-06-25 19:07:21.775027 New work for worker! Difficulty: 1.430048 Share difficulty: 1048.780971 Total block value: 25.000500 BTC including 1 transactions
2013-06-25 19:07:21.778033 New work for worker! Difficulty: 1.430048 Share difficulty: 1048.780971 Total block value: 25.000500 BTC including 1 transactions
2013-06-25 19:07:21.780870 New work for worker! Difficulty: 1.430048 Share difficulty: 1048.780971 Total block value: 25.000500 BTC including 1 transactions
2013-06-25 19:07:21.783816 New work for worker! Difficulty: 1.430048 Share difficulty: 1048.780971 Total block value: 25.000500 BTC including 1 transactions
2013-06-25 19:07:21.788586 New work for worker! Difficulty: 5.000000 Share difficulty: 1048.780971 Total block value: 25.000500 BTC including 1 transactions
2013-06-25 19:07:24.523397 Peer sent entire transaction c046b6219388a196710f6df1542ba8b2f8bc9e5ff8cd413644e141bb3a80b254 that was already received
2013-06-25 19:07:25.961603 P2Pool: 17347 shares in chain (17351 verified/17351 total) Peers: 58 (4 incoming)
2013-06-25 19:07:25.961688 Local: 6137MH/s in last 10.0 minutes Local dead on arrival: ~3.8% (2-7%) Expected time to share: 12.3 minutes
2013-06-25 19:07:25.961730 Shares: 8 (1 orphan, 0 dead) Stale rate: ~12.5% (2-48%) Efficiency: ~102.6% (62-115%) Current payout: 0.2532 BTC
2013-06-25 19:07:25.961757 Pool: 551GH/s Stale rate: 14.7% Expected time to block: 1.7 days
2013-06-25 19:07:27.725795 New work for worker! Difficulty: 1.401363 Share difficulty: 1039.385193 Total block value: 25.001500 BTC including 3 transactions
2013-06-25 19:07:27.728756 New work for worker! Difficulty: 1.401363 Share difficulty: 1039.385193 Total block value: 25.001500 BTC including 3 transactions
2013-06-25 19:07:27.731579 New work for worker! Difficulty: 1.401363 Share difficulty: 1039.385193 Total block value: 25.001500 BTC including 3 transactions
2013-06-25 19:07:27.734343 New work for worker! Difficulty: 1.401363 Share difficulty: 1039.385193 Total block value: 25.001500 BTC including 3 transactions
2013-06-25 19:07:27.737214 New work for worker! Difficulty: 5.000000 Share difficulty: 1039.385193 Total block value: 25.001500 BTC including 3 transactions
2013-06-25 19:07:32.898191 New work for worker! Difficulty: 1.432098 Share difficulty: 1043.302225 Total block value: 25.001500 BTC including 3 transactions
2013-06-25 19:07:32.901337 New work for worker! Difficulty: 1.432098 Share difficulty: 1043.302225 Total block value: 25.001500 BTC including 3 transactions
2013-06-25 19:07:32.906160 New work for worker! Difficulty: 1.432098 Share difficulty: 1043.302225 Total block value: 25.001500 BTC including 3 transactions
2013-06-25 19:07:32.909223 New work for worker! Difficulty: 1.432098 Share difficulty: 1043.302225 Total block value: 25.001500 BTC including 3 transactions
2013-06-25 19:07:32.912061 New work for worker! Difficulty: 5.000000 Share difficulty: 1043.302225 Total block value: 25.001500 BTC including 3 transactions
2013-06-25 19:07:33.963725 P2Pool: 17349 shares in chain (17353 verified/17353 total) Peers: 58 (4 incoming)
2013-06-25 19:07:33.963799 Local: 6126MH/s in last 10.0 minutes Local dead on arrival: ~3.9% (2-7%) Expected time to share: 12.1 minutes
2013-06-25 19:07:33.963832 Shares: 8 (2 orphan, 0 dead) Stale rate: ~25.0% (7-60%) Efficiency: ~88.3% (48-110%) Current payout: 0.2505 BTC
2013-06-25 19:07:33.963876 Pool: 553GH/s Stale rate: 15.1% Expected time to block: 1.7 days
is this a bug?
ok, had 3 orphans in 170 shares or something as i recall
so, i restart server with bitcoind 0.8.3
and on share 4:
2013-06-25 18:02:03.554832 Skipping from block 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab to block aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719!
2013-06-25 18:02:03.557871 New work for worker! Difficulty: 1.772574 Share difficulty: 1063.088180 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:03.560598 New work for worker! Difficulty: 1.772574 Share difficulty: 1063.088180 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:03.563201 New work for worker! Difficulty: 1.772574 Share difficulty: 1063.088180 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:03.565803 New work for worker! Difficulty: 1.772574 Share difficulty: 1063.088180 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:03.568432 New work for worker! Difficulty: 5.000000 Share difficulty: 1063.088180 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:07.416689 Punishing share for 'Block-stale detected! aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719 < 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab'! Jumping from 8aa0ee38 to 287fcce9!
2013-06-25 18:02:07.634945 Punishing share for 'Block-stale detected! aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719 < 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab'! Jumping from 8aa0ee38 to 287fcce9!
2013-06-25 18:02:08.146924 Punishing share for 'Block-stale detected! aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719 < 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab'! Jumping from 8aa0ee38 to 287fcce9!
2013-06-25 18:02:08.147316 Skipping from block 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab to block aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719!
2013-06-25 18:02:09.185104 Punishing share for 'Block-stale detected! aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719 < 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab'! Jumping from 8aa0ee38 to 287fcce9!
2013-06-25 18:02:09.191632 Punishing share for 'Block-stale detected! aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719 < 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab'! Jumping from 8aa0ee38 to 287fcce9!
2013-06-25 18:02:09.659806 GOT SHARE! Crazed Hookers 5183904d prev 287fcce9 age 6.09s
2013-06-25 18:02:09.707200 New work for worker! Difficulty: 1.898801 Share difficulty: 1063.852358 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:09.710064 New work for worker! Difficulty: 1.898801 Share difficulty: 1063.852358 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:09.712893 New work for worker! Difficulty: 1.898801 Share difficulty: 1063.852358 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:09.715610 New work for worker! Difficulty: 1.898801 Share difficulty: 1063.852358 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:09.718332 New work for worker! Difficulty: 5.000000 Share difficulty: 1063.852358 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:10.466509 P2Pool: 17327 shares in chain (17332 verified/17332 total) Peers: 57 (3 incoming)
2013-06-25 18:02:10.466586 Local: 6324MH/s in last 10.0 minutes Local dead on arrival: ~3.8% (2-7%) Expected time to share: 12.0 minutes
2013-06-25 18:02:10.466617 Shares: 4 (0 orphan, 0 dead) Stale rate: ~0.0% (0-49%) Efficiency: ~120.3% (61-121%) Current payout: 0.2596 BTC
2013-06-25 18:02:10.466645 Pool: 578GH/s Stale rate: 16.9% Expected time to block: 1.7 days
2013-06-25 18:02:13.322844 Punishing share for 'Block-stale detected! aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719 < 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab'! Jumping from 4af26ed4 to 8aa0ee38!
2013-06-25 18:02:13.359771 New work for worker! Difficulty: 2.061223 Share difficulty: 1063.852358 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:13.362627 New work for worker! Difficulty: 2.061223 Share difficulty: 1063.852358 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:13.367018 New work for worker! Difficulty: 2.061223 Share difficulty: 1063.852358 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:13.369778 New work for worker! Difficulty: 2.061223 Share difficulty: 1063.852358 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:13.372481 New work for worker! Difficulty: 5.000000 Share difficulty: 1063.852358 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:14.206935 Punishing share for 'Block-stale detected! aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719 < 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab'! Jumping from 4af26ed4 to 8aa0ee38!
2013-06-25 18:02:14.212014 Punishing share for 'Block-stale detected! aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719 < 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab'! Jumping from 4af26ed4 to 8aa0ee38!
2013-06-25 18:02:18.472999 P2Pool: 17321 shares in chain (17326 verified/17326 total) Peers: 57 (3 incoming)
2013-06-25 18:02:18.473077 Local: 6244MH/s in last 10.0 minutes Local dead on arrival: ~3.9% (2-7%) Expected time to share: 12.2 minutes
2013-06-25 18:02:18.473107 Shares: 4 (1 orphan, 0 dead) Stale rate: ~25.0% (4-70%) Efficiency: ~90.2% (36-115%) Current payout: 0.2569 BTC
2013-06-25 18:02:18.473150 Pool: 578GH/s Stale rate: 16.9% Expected time to block: 1.7 days
2013-06-25 18:02:19.185085 Punishing share for 'Block-stale detected! aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719 < 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab'! Jumping from 4af26ed4 to 8aa0ee38!
2013-06-25 18:02:19.188387 Punishing share for 'Block-stale detected! aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719 < 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab'! Jumping from 4af26ed4 to 8aa0ee38!
so, I've submitted a share based on the new block, but I get orphaned again, and I'm still 'punishing' other shares
so, i restart server with bitcoind 0.8.3
and on share 4:
2013-06-25 18:02:03.554832 Skipping from block 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab to block aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719!
2013-06-25 18:02:03.557871 New work for worker! Difficulty: 1.772574 Share difficulty: 1063.088180 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:03.560598 New work for worker! Difficulty: 1.772574 Share difficulty: 1063.088180 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:03.563201 New work for worker! Difficulty: 1.772574 Share difficulty: 1063.088180 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:03.565803 New work for worker! Difficulty: 1.772574 Share difficulty: 1063.088180 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:03.568432 New work for worker! Difficulty: 5.000000 Share difficulty: 1063.088180 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:07.416689 Punishing share for 'Block-stale detected! aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719 < 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab'! Jumping from 8aa0ee38 to 287fcce9!
2013-06-25 18:02:07.634945 Punishing share for 'Block-stale detected! aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719 < 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab'! Jumping from 8aa0ee38 to 287fcce9!
2013-06-25 18:02:08.146924 Punishing share for 'Block-stale detected! aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719 < 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab'! Jumping from 8aa0ee38 to 287fcce9!
2013-06-25 18:02:08.147316 Skipping from block 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab to block aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719!
2013-06-25 18:02:09.185104 Punishing share for 'Block-stale detected! aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719 < 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab'! Jumping from 8aa0ee38 to 287fcce9!
2013-06-25 18:02:09.191632 Punishing share for 'Block-stale detected! aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719 < 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab'! Jumping from 8aa0ee38 to 287fcce9!
2013-06-25 18:02:09.659806 GOT SHARE! Crazed Hookers 5183904d prev 287fcce9 age 6.09s
2013-06-25 18:02:09.707200 New work for worker! Difficulty: 1.898801 Share difficulty: 1063.852358 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:09.710064 New work for worker! Difficulty: 1.898801 Share difficulty: 1063.852358 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:09.712893 New work for worker! Difficulty: 1.898801 Share difficulty: 1063.852358 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:09.715610 New work for worker! Difficulty: 1.898801 Share difficulty: 1063.852358 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:09.718332 New work for worker! Difficulty: 5.000000 Share difficulty: 1063.852358 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:10.466509 P2Pool: 17327 shares in chain (17332 verified/17332 total) Peers: 57 (3 incoming)
2013-06-25 18:02:10.466586 Local: 6324MH/s in last 10.0 minutes Local dead on arrival: ~3.8% (2-7%) Expected time to share: 12.0 minutes
2013-06-25 18:02:10.466617 Shares: 4 (0 orphan, 0 dead) Stale rate: ~0.0% (0-49%) Efficiency: ~120.3% (61-121%) Current payout: 0.2596 BTC
2013-06-25 18:02:10.466645 Pool: 578GH/s Stale rate: 16.9% Expected time to block: 1.7 days
2013-06-25 18:02:13.322844 Punishing share for 'Block-stale detected! aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719 < 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab'! Jumping from 4af26ed4 to 8aa0ee38!
2013-06-25 18:02:13.359771 New work for worker! Difficulty: 2.061223 Share difficulty: 1063.852358 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:13.362627 New work for worker! Difficulty: 2.061223 Share difficulty: 1063.852358 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:13.367018 New work for worker! Difficulty: 2.061223 Share difficulty: 1063.852358 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:13.369778 New work for worker! Difficulty: 2.061223 Share difficulty: 1063.852358 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:13.372481 New work for worker! Difficulty: 5.000000 Share difficulty: 1063.852358 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:14.206935 Punishing share for 'Block-stale detected! aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719 < 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab'! Jumping from 4af26ed4 to 8aa0ee38!
2013-06-25 18:02:14.212014 Punishing share for 'Block-stale detected! aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719 < 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab'! Jumping from 4af26ed4 to 8aa0ee38!
2013-06-25 18:02:18.472999 P2Pool: 17321 shares in chain (17326 verified/17326 total) Peers: 57 (3 incoming)
2013-06-25 18:02:18.473077 Local: 6244MH/s in last 10.0 minutes Local dead on arrival: ~3.9% (2-7%) Expected time to share: 12.2 minutes
2013-06-25 18:02:18.473107 Shares: 4 (1 orphan, 0 dead) Stale rate: ~25.0% (4-70%) Efficiency: ~90.2% (36-115%) Current payout: 0.2569 BTC
2013-06-25 18:02:18.473150 Pool: 578GH/s Stale rate: 16.9% Expected time to block: 1.7 days
2013-06-25 18:02:19.185085 Punishing share for 'Block-stale detected! aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719 < 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab'! Jumping from 4af26ed4 to 8aa0ee38!
2013-06-25 18:02:19.188387 Punishing share for 'Block-stale detected! aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719 < 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab'! Jumping from 4af26ed4 to 8aa0ee38!
so, I've submitted a share based on the new block, but I get orphaned again, and I'm still 'punishing' other shares
someone make a ready-to-run, easy-to-configure p2p-pool-node for raspberry.
put image on SD, insert, boot up, enter essential node stuff (.pdf format how-to supplied on d/l page), point miners - go!
There's no way you could run bitcoind and p2pool on a Raspberry Pi and still expect to have a decent latency.put image on SD, insert, boot up, enter essential node stuff (.pdf format how-to supplied on d/l page), point miners - go!
Indeed. 1GB RAM would be barely sufficient...
someone make a ready-to-run, easy-to-configure p2p-pool-node for raspberry.
put image on SD, insert, boot up, enter essential node stuff (.pdf format how-to supplied on d/l page), point miners - go!
There's no way you could run bitcoind and p2pool on a Raspberry Pi and still expect to have a decent latency. put image on SD, insert, boot up, enter essential node stuff (.pdf format how-to supplied on d/l page), point miners - go!
I am a bit afraid of memory and cpu requirements of python for rPI - I was thinking about google golang implementation.
Not much progress yet, but maybe ... GO!
Not much progress yet, but maybe ... GO!
someone make a ready-to-run, easy-to-configure p2p-pool-node for raspberry.
put image on SD, insert, boot up, enter essential node stuff (.pdf format how-to supplied on d/l page), point miners - go!
put image on SD, insert, boot up, enter essential node stuff (.pdf format how-to supplied on d/l page), point miners - go!
OK, so I've been looking at my orphans for the last 10 days or so.... about 33% of them occur after a block solve.
i guess i should also mention that 50% of them are orphaned by
1CTgYxMTY5j6SLytKeMsBWAXuUc6yNKcAe
and i know he isnt using an asic, so why so slow?
How do you know it was that address, and is it wrong to assume that you have his ip address? If so ban him don't send any more work his way. Not that it matters but that address has a huge balance by the way...
nah, he's a major contributor to p2pool. i think he's been mining it for years. i'm just whining and wish he had a faster setup. =p
I don't even know what IP he mines to, which I guess is part of the problem. I think he's on a private node, probably with just 6 outgoing connections.
oh, I know it was that address since my orphan showed up in the 'headers' list... then I go to the parent share and click on child, and it shows what replaced your orphaned share (if it works the way I think it does, that replacement is actually dictated by the share that comes after it)
Here's another good example (not my shares):
(presumably two would have been orphaned, anyway, but..) These three shares, in order of time my server saw them:
Share 5573d59d Parent: f923ec04
Time first seen: Tue Jun 25 2013 03:26:34 GMT-0500 (Central Daylight Time) (1372148794.021445)
Share d0a23adf Parent: f923ec04
Time first seen: Tue Jun 25 2013 03:26:34 GMT-0500 (Central Daylight Time) (1372148794.186212)
Share 22d14440 Parent: f923ec04
Time first seen: Tue Jun 25 2013 03:26:34 GMT-0500 (Central Daylight Time) (1372148794.205658)
(183ms apart)
got orphaned by this one:
Share 7cb9dbd5 Parent: f923ec04
Time first seen: Tue Jun 25 2013 03:26:48 GMT-0500 (Central Daylight Time) (1372148808.8004)
Payout address: 1CTgYxMTY5j6SLytKeMsBWAXuUc6yNKcAe
14780ms late
it got orphaned because the next share was:
Share 5ccfc4c1 Parent: 7cb9dbd5
Time first seen: Tue Jun 25 2013 03:26:51 GMT-0500 (Central Daylight Time) (1372148811.190973)
Payout address: 1CTgYxMTY5j6SLytKeMsBWAXuUc6yNKcAe
.......
that's a really long lag time.. I was thinking he must have been working on a different parent share, but that says they all have the same one.... *scratch*
oh!
I bet it was caused by this:
http://blockchain.info/block-index/394604/0000000000000099ea7426c7e7289e03c25caebe329b5f0b7f10696d20626879
the same thing I was whining about =p
----------------------------
1 orphan in 107 shares (107 now, 101 then), this:
2013-06-25 08:58:19.715307 Punishing share for 'Block-stale detected! ed82da82bd35e7059f84ff75721bdc5e2ed51e5a5bb801a6c < 32205ef944185696477f67f3081b9d0812403497f4cc931cd9'! Jumping from f5e744ca to
aea3ccc9!
2013-06-25 08:58:19.749535 New work for worker! Difficulty: 1.351312 Share difficulty: 1075.192002 Total block value: 25.008000 BTC including 4 transactions
2013-06-25 08:58:19.753518 New work for worker! Difficulty: 1.351312 Share difficulty: 1075.192002 Total block value: 25.008000 BTC including 4 transactions
2013-06-25 08:58:19.757446 New work for worker! Difficulty: 1.351312 Share difficulty: 1075.192002 Total block value: 25.008000 BTC including 4 transactions
2013-06-25 08:58:19.761187 New work for worker! Difficulty: 1.351312 Share difficulty: 1075.192002 Total block value: 25.008000 BTC including 4 transactions
2013-06-25 08:58:19.766552 New work for worker! Difficulty: 5.000000 Share difficulty: 1075.192002 Total block value: 25.008000 BTC including 4 transactions
2013-06-25 08:58:19.796149 New work for worker! Difficulty: 1.351312 Share difficulty: 1075.192002 Total block value: 25.002000 BTC including 4 transactions
2013-06-25 08:58:19.800348 New work for worker! Difficulty: 1.351312 Share difficulty: 1075.192002 Total block value: 25.002000 BTC including 4 transactions
2013-06-25 08:58:19.804610 New work for worker! Difficulty: 1.351312 Share difficulty: 1075.192002 Total block value: 25.002000 BTC including 4 transactions
2013-06-25 08:58:19.809372 New work for worker! Difficulty: 1.351312 Share difficulty: 1075.192002 Total block value: 25.002000 BTC including 4 transactions
2013-06-25 08:58:20.000072 New work for worker! Difficulty: 5.000000 Share difficulty: 1075.192002 Total block value: 25.002000 BTC including 4 transactions
2013-06-25 08:58:20.802166 Punishing share for 'Block-stale detected! ed82da82bd35e7059f84ff75721bdc5e2ed51e5a5bb801a6c < 32205ef944185696477f67f3081b9d0812403497f4cc931cd9'! Jumping from 541b96e9 to
f5e744ca!
2013-06-25 08:58:20.844785 New work for worker! Difficulty: 1.351312 Share difficulty: 1076.726276 Total block value: 25.002000 BTC including 4 transactions
2013-06-25 08:58:20.850027 New work for worker! Difficulty: 1.351312 Share difficulty: 1076.726276 Total block value: 25.002000 BTC including 4 transactions
2013-06-25 08:58:20.856650 New work for worker! Difficulty: 1.351312 Share difficulty: 1076.726276 Total block value: 25.002000 BTC including 4 transactions
2013-06-25 08:58:20.861682 New work for worker! Difficulty: 1.351312 Share difficulty: 1076.726276 Total block value: 25.002000 BTC including 4 transactions
2013-06-25 08:58:20.866957 New work for worker! Difficulty: 5.000000 Share difficulty: 1076.726276 Total block value: 25.002000 BTC including 4 transactions
2013-06-25 08:58:23.376789 Punishing share for 'Block-stale detected! ed82da82bd35e7059f84ff75721bdc5e2ed51e5a5bb801a6c < 32205ef944185696477f67f3081b9d0812403497f4cc931cd9'! Jumping from 541b96e9 to
f5e744ca!
2013-06-25 08:58:23.379542 Punishing share for 'Block-stale detected! ed82da82bd35e7059f84ff75721bdc5e2ed51e5a5bb801a6c < 32205ef944185696477f67f3081b9d0812403497f4cc931cd9'! Jumping from 541b96e9 to
f5e744ca!
2013-06-25 08:58:24.442380 GOT SHARE! Crazed Hookers 4380a491 prev f5e744ca age 3.58s
2013-06-25 08:58:24.490625 New work for worker! Difficulty: 1.268760 Share difficulty: 1069.919469 Total block value: 25.002000 BTC including 4 transactions
2013-06-25 08:58:24.494000 New work for worker! Difficulty: 1.268760 Share difficulty: 1069.919469 Total block value: 25.002000 BTC including 4 transactions
2013-06-25 08:58:24.497168 New work for worker! Difficulty: 1.268760 Share difficulty: 1069.919469 Total block value: 25.002000 BTC including 4 transactions
2013-06-25 08:58:24.501941 New work for worker! Difficulty: 1.268760 Share difficulty: 1069.919469 Total block value: 25.002000 BTC including 4 transactions
2013-06-25 08:58:24.505167 New work for worker! Difficulty: 5.000000 Share difficulty: 1069.919469 Total block value: 25.002000 BTC including 4 transactions
2013-06-25 08:58:24.599258 New work for worker! Difficulty: 1.294867 Share difficulty: 1076.474487 Total block value: 25.002000 BTC including 4 transactions
2013-06-25 08:58:24.602612 New work for worker! Difficulty: 1.294867 Share difficulty: 1076.474487 Total block value: 25.002000 BTC including 4 transactions
2013-06-25 08:58:24.605772 New work for worker! Difficulty: 1.294867 Share difficulty: 1076.474487 Total block value: 25.002000 BTC including 4 transactions
2013-06-25 08:58:24.608983 New work for worker! Difficulty: 1.294867 Share difficulty: 1076.474487 Total block value: 25.002000 BTC including 4 transactions
2013-06-25 08:58:24.703523 New work for worker! Difficulty: 5.000000 Share difficulty: 1076.474487 Total block value: 25.002000 BTC including 4 transactions
2013-06-25 08:58:25.710917 P2Pool: 17337 shares in chain (17342 verified/17342 total) Peers: 68 (14 incoming)
2013-06-25 08:58:25.711003 Local: 6319MH/s in last 10.0 minutes Local dead on arrival: ~7.3% (4-11%) Expected time to share: 12.2 minutes
2013-06-25 08:58:25.711045 Shares: 101 (1 orphan, 9 dead) Stale rate: ~9.9% (5-18%) Efficiency: ~110.4% (101-116%) Current payout: 0.2833 BTC
2013-06-25 08:58:25.711082 Pool: 583GH/s Stale rate: 18.4% Expected time to block: 1.6 days
maybe it's more like 50% of the orphans
p2pool / Commits
Jun 24, 2013
fixed "invalid fee" message in test case
f78a4e86eb Browse code
forrestv authored 17 hours ago
reinstated share voting logic
7c28b06588 Browse code
forrestv authored 17 hours ago
the update start?
Jun 24, 2013
fixed "invalid fee" message in test case
f78a4e86eb Browse code
forrestv authored 17 hours ago
reinstated share voting logic
7c28b06588 Browse code
forrestv authored 17 hours ago
the update start?
When I was running my local node, my bitcoind had 1 maxconnection, listen=0, and connected to my germany server. p2pool had 6 outgoing and default incoming. i don't think i ever ended up with more than 10 incoming though. i shut it down after a day since I was still getting around 1-2% DOA, but also about 10-15% orphans... which was more than the typical 5% DOA and 3% orphans or so I got mining to my remote server.
I think if I tried it again it would be with the 1 bitcoind connection and 3 p2pool connections, one to my server in germany, one to my server in jacksonville, and one to my friend's server in quebec. i suspect this would cut the # of orphans, maybe down to 10% or so... this assumption for when my link is performing fine 24/7 instead of when bandwidth is oversold like it is now
I restarted server roughly 3 1/2 hrs ago, at 4:40PM local time,
here is what my link has been like since then (I started the ping about 30 minutes before restarting the server):
it is scaled to 400ms and 10% packetloss. the top bar is jitter (scaled to 50ms, goes off the chart a lot). note that this is a ping to my first hop, so to get the ping times to my server, add 150ms to that
in this time the server has gotten 29 shares, 0 orphans, 4 DOA. 17 of those are mine, and 2 of the DOA are mine. 12 are others, and 2 of the DOA are them (1G8D has gotten incredibly unlucky with 2 DOA out of 8 shares, even though it looks like his DOA rate is only about 3% to server)
anyway, even my 11.5% DOA or so would have an efficiency of well over 100%, with that ^^ crap link shown above
I think if I tried it again it would be with the 1 bitcoind connection and 3 p2pool connections, one to my server in germany, one to my server in jacksonville, and one to my friend's server in quebec. i suspect this would cut the # of orphans, maybe down to 10% or so... this assumption for when my link is performing fine 24/7 instead of when bandwidth is oversold like it is now
I restarted server roughly 3 1/2 hrs ago, at 4:40PM local time,
here is what my link has been like since then (I started the ping about 30 minutes before restarting the server):
it is scaled to 400ms and 10% packetloss. the top bar is jitter (scaled to 50ms, goes off the chart a lot). note that this is a ping to my first hop, so to get the ping times to my server, add 150ms to that
in this time the server has gotten 29 shares, 0 orphans, 4 DOA. 17 of those are mine, and 2 of the DOA are mine. 12 are others, and 2 of the DOA are them (1G8D has gotten incredibly unlucky with 2 DOA out of 8 shares, even though it looks like his DOA rate is only about 3% to server)
anyway, even my 11.5% DOA or so would have an efficiency of well over 100%, with that ^^ crap link shown above
In the next couple days, I'm going to release a hard-forking change to P2Pool that will make the following changes:
Global changes
* Increase last transaction extranonce length from 4 bytes to 8 bytes, so full 4-byte Stratum workunits can be efficiently generated (which will prevent the need for the avalon branch)
* Delay payout calculation 1 share so that payouts can be calculated ahead of time, reducing latency between a new share being received and work being distributed to miners
* Option to set a "dust target," which increases your share difficulty so that you don't get payouts below that target
Bitcoin network
* Increase SHARE_PERIOD (average time between shares) from 10 seconds to 30 seconds, in order to make it more fair for high-latency miners (read: ASICs)
Litecoin network
* Decrease SPREAD (number of blocks a share's payout is spread over, on average) from 12 blocks to 3 blocks, significantly decreasing the dust payouts generated for miners who get a share less often than every 3 blocks the pool finds
Warnings will be spammed to miners (UPGRADE REQUIRED) once 50% of each P2Pool's mining power has upgraded and the changes will take effect 12 hours after 95% of the mining power has been upgraded, as usual.
If anyone has any recommendations for additional changes or comments on these, please respond.
Global changes
* Increase last transaction extranonce length from 4 bytes to 8 bytes, so full 4-byte Stratum workunits can be efficiently generated (which will prevent the need for the avalon branch)
* Delay payout calculation 1 share so that payouts can be calculated ahead of time, reducing latency between a new share being received and work being distributed to miners
* Option to set a "dust target," which increases your share difficulty so that you don't get payouts below that target
Bitcoin network
* Increase SHARE_PERIOD (average time between shares) from 10 seconds to 30 seconds, in order to make it more fair for high-latency miners (read: ASICs)
Litecoin network
* Decrease SPREAD (number of blocks a share's payout is spread over, on average) from 12 blocks to 3 blocks, significantly decreasing the dust payouts generated for miners who get a share less often than every 3 blocks the pool finds
Warnings will be spammed to miners (UPGRADE REQUIRED) once 50% of each P2Pool's mining power has upgraded and the changes will take effect 12 hours after 95% of the mining power has been upgraded, as usual.
If anyone has any recommendations for additional changes or comments on these, please respond.
YES!
Guess I'll be able to throw a few Gh of reduced variability your way after all!
It is most likely Bitcoind not p2pool. My bitcoind was using nearly all of my 2mbit upstream, so I lowered the maxconnections variable from 125 (default) to 20 and it dropped that down to around 200kbps. I haven't noticed any increase in orphans (or bitcoind latency) with the change.
That's exactly what I recommend in the guide. Lowering the max number of P2Pool connections to 12 (4 outgoing, 8 incoming, which I'm currently testing with no measurable change in efficiency) would be safer too with salfter limited bandwidth.
[...]
One thing: my P2Pool node is at home, but my Jalapeños are at work. Ping times tend to run 30-50 ms; both LANs are connected through Cox. Would even this little bit of added latency be enough to throw my efficiency into the basement?
One thing: my P2Pool node is at home, but my Jalapeños are at work. Ping times tend to run 30-50 ms; both LANs are connected through Cox. Would even this little bit of added latency be enough to throw my efficiency into the basement?
According to zvs results in a similar setup, no: he achieved high efficiency with much higher ping times (and one other user reported high efficiency at around 30ms too).
Can you find out if your network connection has some headroom left? The most reliable way would be to monitor your P2Pool host public network interface with a low monitor interval to detect spikes under the 10s interval, then check what your network usage is by graphing the data: spikes up to your downlink or uplink max capacity should be the exception.
nload says my P2Pool node (running just bitcoind, P2Pool, and cgminer & CryptoSwitcher (the latter two for GPU-mining altcoins)) is averaging 1.04 Mbps upstream, which is about two-thirds of what's available to me IIRC. This is with P2Pool reporting 7 outbound peers and 12 inbound peers. Should it be using this much bandwidth?
It is most likely Bitcoind not p2pool. My bitcoind was using nearly all of my 2mbit upstream, so I lowered the maxconnections variable from 125 (default) to 20 and it dropped that down to around 200kbps. I haven't noticed any increase in orphans (or bitcoind latency) with the change.
[...]
One thing: my P2Pool node is at home, but my Jalapeños are at work. Ping times tend to run 30-50 ms; both LANs are connected through Cox. Would even this little bit of added latency be enough to throw my efficiency into the basement?
One thing: my P2Pool node is at home, but my Jalapeños are at work. Ping times tend to run 30-50 ms; both LANs are connected through Cox. Would even this little bit of added latency be enough to throw my efficiency into the basement?
According to zvs results in a similar setup, no: he achieved high efficiency with much higher ping times (and one other user reported high efficiency at around 30ms too).
Can you find out if your network connection has some headroom left? The most reliable way would be to monitor your P2Pool host public network interface with a low monitor interval to detect spikes under the 10s interval, then check what your network usage is by graphing the data: spikes up to your downlink or uplink max capacity should be the exception.
nload says my P2Pool node (running just bitcoind, P2Pool, and cgminer & CryptoSwitcher (the latter two for GPU-mining altcoins)) is averaging 1.04 Mbps upstream, which is about two-thirds of what's available to me IIRC. This is with P2Pool reporting 7 outbound peers and 12 inbound peers. Should it be using this much bandwidth?
Hi has anyone Problems with Bitcoind connectet to other Bitcoind nodes over Tor and connectet to local p2pool?
These are world changing indeed. I've always felt that 10s interval was a bit low (and argued about it with forrestv on IRC in the early days of P2Pool IIRC) but this was a compromise (new miners will have to wait a bit longer to get their full payouts with the new 30s interval). The dust removing and payout computation delay are very nice too.
In fact I believe that most node efficiencies will converge to 100% with these changes which is really good (although it will probably reduce my income as I'm in the 110-115% range most of the time...).
As tuning P2Pool/bitcoind won't bring much benefit this will help with people still insisting on running nodes generating low block sizes and make our income even slightly higher. This could even deprecate much of what I spent quite some time writing in my guide :-(
[...]
One thing: my P2Pool node is at home, but my Jalapeños are at work. Ping times tend to run 30-50 ms; both LANs are connected through Cox. Would even this little bit of added latency be enough to throw my efficiency into the basement?
One thing: my P2Pool node is at home, but my Jalapeños are at work. Ping times tend to run 30-50 ms; both LANs are connected through Cox. Would even this little bit of added latency be enough to throw my efficiency into the basement?
According to zvs results in a similar setup, no: he achieved high efficiency with much higher ping times (and one other user reported high efficiency at around 30ms too).
Can you find out if your network connection has some headroom left? The most reliable way would be to monitor your P2Pool host public network interface with a low monitor interval to detect spikes under the 10s interval, then check what your network usage is by graphing the data: spikes up to your downlink or uplink max capacity should be the exception.
By "don't use different payout addresses," are you suggesting that I should use an address from the bitcoind wallet, or only that I shouldn't use the "mine-to-the-address-in-the-username" feature (which I don't use)?
If you have only one miner you are using a single payout address whichever way you configured it. If you have several miners, either use names to connect to the P2Pool node to use its configured (or automatically generated, but not advisable) payout address (my preferred configuration which makes nice graphs for each miner) or use the same address for all miners (if you don't want multiple graphs).
In any case, it looks like I should see some benefit from the upcoming changes to P2Pool. I'd like to see the concept succeed, so I think I can stick with it at least a little while longer.
These are world changing indeed. I've always felt that 10s interval was a bit low (and argued about it with forrestv on IRC in the early days of P2Pool IIRC) but this was a compromise (new miners will have to wait a bit longer to get their full payouts with the new 30s interval). The dust removing and payout computation delay are very nice too.
Sorry about the confusion and your time spent writing a long post - the sharechain length is set in terms of number of shares, not time, and I meant that the number of shares (8640) will remain the same, so you have nothing to worry about! The new sharechain will indeed be 3 days long.
NICE!!
Thanks!!
Josh
I'm seeing only 84% efficiency with mine. What settings are you using? My miner name has +256 appended to it. A poster in the BFL forums is using /6000 and is getting results more like yours than mine. Given that share difficulty is only 1080 as I write this, though, wouldn't setting difficulty too high risk throwing out valid shares?
What would be a good input to have to guess how good these ASICs are would be people comparing what their efficiency was with low-latency mining devices (GPUs/Icarus/Cairnsmore1/Ztex/...) and what is their efficiency with their BFL ASIC without any p2pool node reconfiguration.
If they have a mixed setup, knowing the total hashrate of the low-latency devices and the total hashrate of the BFL ASICs can do too.
Warning: don't use different payout addresses on your node: it currently adds latency in the P2Pool process and would lower efficiency.
Currently they don't seem horrible: 84% efficiency is the worst I'm aware of. It's bad but not far from what is good enough to make it almost as good as most pools (I consider the 90-95% range to be where P2Pool starts to be the best solution for mining).
Try to tune your setup according to my guide to see if you can reach a better efficiency (see my sig).
I've done that...average bitcoind latency seems to be hanging around 300 ms since the upgrade to 0.8.2. With 0.8.1, I was seeing multiple-second latencies. Over the weekend, efficiency went up slightly to around 86%. I've switched from +256 to /6000 to see if that makes any difference; it's only been running a few minutes, but the 204 rejected shares to 642 accepted shares so far isn't much different than what I was already getting. I double-checked my router QoS settings; p2pool traffic is running at a high priority.
One thing: my P2Pool node is at home, but my Jalapeños are at work. Ping times tend to run 30-50 ms; both LANs are connected through Cox. Would even this little bit of added latency be enough to throw my efficiency into the basement?
By "don't use different payout addresses," are you suggesting that I should use an address from the bitcoind wallet, or only that I shouldn't use the "mine-to-the-address-in-the-username" feature (which I don't use)?
In any case, it looks like I should see some benefit from the upcoming changes to P2Pool. I'd like to see the concept succeed, so I think I can stick with it at least a little while longer.
Jump to: