iongchun
Member
Offline
Activity: 75
Merit: 10
|
|
December 11, 2012, 04:18:02 AM |
|
unfortunately p2pool wasted work do not go below 15-20% as was before hardfork
Stale P2Pool shares are not "wasted" - they still can solve blocks and get us all a payout. They're just don't count for P2Pool credit, which affects everyone to some degree, so everything is optimal and fair as long as your efficiency is close to 100%. Since people will keep talking about this "problem", how about showing "Local status" on the static page based on efficiency? Ex. "Good" for >110%, "Normal" for 100~110%, "Below Normal" for 90~100%, "Bad" for <90%.
|
Bitcoin: 1NFMpJUW7sTKmnVKj12MxhPvCvzAKQ5gUV Namecoin: N5Tnt3JyMeizsoAFAZDr7CSxjzDtPSisK8 Mining with P2Pool. Graph. Blocks.
|
|
|
cabin
|
|
December 11, 2012, 12:59:42 PM |
|
when I set maxconnections=10 my p2pool is not started, just stay in 2012-12-09 21:05:51.285000 p2pool (version 9.4) 2012-12-09 21:05:51.300000 2012-12-09 21:05:51.300000 Testing bitcoind RPC connection to 'http://127.0.0.1:8332/' with username 'zzzzz'... 2012-12-09 21:05:51.378000 ...success! 2012-12-09 21:05:51.394000 Current block hash: 23vdgbfgbfhnfgn563hyjntjntgnbgfn6443h46h3nynn4tbtbrb 2012-12-09 21:05:51.394000 Current block height: 211544 2012-12-09 21:05:51.394000 2012-12-09 21:05:51.394000 Testing bitcoind P2P connection to '127.0.0.1:8333'...
If it uses up all 10 before p2pool has a chance to connect then this happens. You can either start p2pool quickly after bitcoin or increase it to 20 or something.
|
|
|
|
rav3n_pl
Legendary
Offline
Activity: 1361
Merit: 1003
Don`t panic! Organize!
|
|
December 11, 2012, 01:16:15 PM |
|
when I set maxconnections=10 my p2pool is not started, just stay in 2012-12-09 21:05:51.285000 p2pool (version 9.4) 2012-12-09 21:05:51.300000 2012-12-09 21:05:51.300000 Testing bitcoind RPC connection to 'http://127.0.0.1:8332/' with username 'zzzzz'... 2012-12-09 21:05:51.378000 ...success! 2012-12-09 21:05:51.394000 Current block hash: 23vdgbfgbfhnfgn563hyjntjntgnbgfn6443h46h3nynn4tbtbrb 2012-12-09 21:05:51.394000 Current block height: 211544 2012-12-09 21:05:51.394000 2012-12-09 21:05:51.394000 Testing bitcoind P2P connection to '127.0.0.1:8333'...
If it uses up all 10 before p2pool has a chance to connect then this happens. You can either start p2pool quickly after bitcoin or increase it to 20 or something. Or restart bitcoind after starting p2pool.
|
|
|
|
Proofer
Member
Offline
Activity: 266
Merit: 36
|
|
December 11, 2012, 04:53:54 PM |
|
Where in my linux p2pool directory can I look to find the human-readable version number, e.g., currently, 9.4?
run_p2pool.py --version This was while p2pool was already running normally: proofer@miner:~/src/p2pool$ run_p2pool.py --version fatal: Not a git repository (or any parent up to mount parent ) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). unknown proofer@miner:~/src/p2pool$: The p2pool directory is renamed from the forrestv-p2pool-6880123 directory that was the expansion of the 9.4 linux tarball.
|
|
|
|
rav3n_pl
Legendary
Offline
Activity: 1361
Merit: 1003
Don`t panic! Organize!
|
|
December 11, 2012, 07:09:19 PM |
|
Where in my linux p2pool directory can I look to find the human-readable version number, e.g., currently, 9.4?
run_p2pool.py --version This was while p2pool was already running normally: proofer@miner:~/src/p2pool$ run_p2pool.py --version fatal: Not a git repository (or any parent up to mount parent ) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). unknown proofer@miner:~/src/p2pool$: The p2pool directory is renamed from the forrestv-p2pool-6880123 directory that was the expansion of the 9.4 linux tarball. Git clone p2pool and copy data directory and use it All problems gone forever.
|
|
|
|
mdude77
Legendary
Offline
Activity: 1540
Merit: 1001
|
|
December 12, 2012, 02:19:25 AM |
|
After 1d 15h 5m 39s, I have 211 shares, 22 orphaned, 3 dead - 11.85% stale rate. That's using the linux "do not use for mining" build in a VM, and p2pool v9.4. Decent in my mind, but not as good as it was pre fork.
Between my 3 miners, I have about 112k shares submitted, about 3k rejected, or 2.67% reject rate. That's pretty good for LP imho. Looking forward to stratum coming on.
M
|
I mine at Kano's Pool because it pays the best and is completely transparent! Come join me!
|
|
|
aTg
Legendary
Offline
Activity: 1358
Merit: 1000
|
|
December 12, 2012, 05:50:08 AM |
|
What happens to the roof of the 400GH / s? It seems to be impossible to overcome when large mining brings lot of computing power other small miners disappear.
|
|
|
|
cabin
|
|
December 12, 2012, 01:09:57 PM |
|
After 1d 15h 5m 39s, I have 211 shares, 22 orphaned, 3 dead - 11.85% stale rate. That's using the linux "do not use for mining" build in a VM, and p2pool v9.4. Decent in my mind, but not as good as it was pre fork.
Between my 3 miners, I have about 112k shares submitted, about 3k rejected, or 2.67% reject rate. That's pretty good for LP imho. Looking forward to stratum coming on.
M
That's an excellent long term stale right.. I think mine is closer to 5%.
|
|
|
|
lenny_
Legendary
Offline
Activity: 1036
Merit: 1000
DARKNETMARKETS.COM
|
|
December 12, 2012, 02:24:49 PM |
|
I have even better stats. On total 13187222 shares, 36281 stale shares = 0.275%. Using Ztex's BTCMiner on BitMinter pool. Unfortunately, my p2pool machine is too weak to get similar results on local p2pool with my FPGAs. Bitcoind latency is ~0.5s.
|
|
|
|
Red Emerald
|
|
December 12, 2012, 08:58:26 PM |
|
I have even better stats. On total 13187222 shares, 36281 stale shares = 0.275%. Using Ztex's BTCMiner on BitMinter pool. Unfortunately, my p2pool machine is too weak to get similar results on local p2pool with my FPGAs. Bitcoind latency is ~0.5s. You can't compare stale rates of bitminter (or any non p2pool) with p2pool. They work differently. My stratum miner is only .068% reject, but that number doesn't mean anything compared to p2pool.
|
|
|
|
mdude77
Legendary
Offline
Activity: 1540
Merit: 1001
|
|
December 13, 2012, 11:13:08 AM |
|
I've come to the conclusion that latency plays a huge factor in stale rate. I think bitcoind was hogging my bandwidth, I turned off port forwarding for it, stopped using -n to connect to multiple p2pool pools, and turned off port forwarding to my backup p2pool.
After 10h 8m 45s, I have 49 shares, 2 orphaned, or 4.08% stale. Been ages since I've been that low.
M
|
I mine at Kano's Pool because it pays the best and is completely transparent! Come join me!
|
|
|
Prattler
|
|
December 13, 2012, 02:00:24 PM |
|
There is still a memory leak. P2pool consuming 2.4 GB memory (RES) after running for 7 days.
|
|
|
|
lenny_
Legendary
Offline
Activity: 1036
Merit: 1000
DARKNETMARKETS.COM
|
|
December 13, 2012, 02:11:35 PM |
|
There is still a memory leak. P2pool consuming 2.4 GB memory (RES) after running for 7 days.
Are you using most recent version 9.4-13-g5703b70?
|
|
|
|
cabin
|
|
December 13, 2012, 05:52:37 PM |
|
I've come to the conclusion that latency plays a huge factor in stale rate. I think bitcoind was hogging my bandwidth, I turned off port forwarding for it, stopped using -n to connect to multiple p2pool pools, and turned off port forwarding to my backup p2pool.
After 10h 8m 45s, I have 49 shares, 2 orphaned, or 4.08% stale. Been ages since I've been that low.
M
I found the same thing.. it is vital to keep that latency down. It makes sense when you think about it too.. if bitcoin is taking 1 second all on its own then you could expect around 10% stales just from that since we have 10s long polls.
|
|
|
|
spiccioli
Legendary
Offline
Activity: 1379
Merit: 1003
nec sine labore
|
|
December 14, 2012, 10:00:21 AM Last edit: December 14, 2012, 10:15:51 AM by spiccioli |
|
Hi, tonight my public p2pool entry point died like this: edit: Version: 9.4-2-g178a105 2012-12-14 04:52:03.869111 New work for worker! Difficulty: 0.999985 Share difficulty: 652.552635 Total block value: 25.076800 BTC including 94 transactions 2012-12-14 04:52:05.412878 P2Pool: 17489 shares in chain (17495 verified/17495 total) Peers: 8 (2 incoming) 2012-12-14 04:52:05.413068 Local: 0H/s in last 10.0 minutes Local dead on arrival: ??? Expected time to share: ??? 2012-12-14 04:52:05.413174 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.3560 BTC 2012-12-14 04:52:05.413258 Pool: 342GH/s Stale rate: 21.2% Expected time to block: 11.7 hours 2012-12-14 04:52:08.417233 P2Pool: 17490 shares in chain (17496 verified/17496 total) Peers: 8 (2 incoming) 2012-12-14 04:52:08.417425 Local: 0H/s in last 10.0 minutes Local dead on arrival: ??? Expected time to share: ??? 2012-12-14 04:52:08.417528 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.3560 BTC 2012-12-14 04:52:08.417625 Pool: 344GH/s Stale rate: 21.4% Expected time to block: 11.7 hours 2012-12-14 04:52:10.746180 Peer sent entire transaction 1b682ee41663264988bbdd9b7f6722ea12245724770e716751a9f52f59507a6f that was already received 2012-12-14 04:52:11.421506 P2Pool: 17491 shares in chain (17497 verified/17497 total) Peers: 8 (2 incoming) 2012-12-14 04:52:11.421713 Local: 0H/s in last 10.0 minutes Local dead on arrival: ??? Expected time to share: ??? 2012-12-14 04:52:11.421819 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.3560 BTC 2012-12-14 04:52:11.421927 Pool: 345GH/s Stale rate: 21.4% Expected time to block: 11.6 hours 2012-12-14 04:52:14.426445 P2Pool: 17492 shares in chain (17498 verified/17498 total) Peers: 8 (2 incoming) 2012-12-14 04:52:14.426664 Local: 0H/s in last 10.0 minutes Local dead on arrival: ??? Expected time to share: ??? 2012-12-14 04:52:14.426780 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.3560 BTC 2012-12-14 04:52:14.426870 Pool: 346GH/s Stale rate: 21.6% Expected time to block: 11.6 hours 2012-12-14 04:52:15.150643 New work for worker! Difficulty: 0.999985 Share difficulty: 660.608885 Total block value: 25.081000 BTC including 95 transactions 2012-12-14 04:52:17.429943 P2Pool: 17492 shares in chain (17498 verified/17498 total) Peers: 8 (2 incoming) 2012-12-14 04:52:17.430130 Local: 0H/s in last 10.0 minutes Local dead on arrival: ??? Expected time to share: ??? 2012-12-14 04:52:17.430234 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.3561 BTC 2012-12-14 04:52:17.430318 Pool: 346GH/s Stale rate: 21.6% Expected time to block: 11.6 hours 2012-12-14 04:52:19.014260 Transaction 1c8de481f32a4c1dde2070c76b114b499bb12c8a5beb8bbc9b9ac7c1ec696e29 rescued from peer latency cache! 2012-12-14 04:52:19.014507 Transaction 1dcb5de585bee1e458dddc89dead66e1184f5fb3eef71ad5317e397e43b7b0cc rescued from peer latency cache! 2012-12-14 04:52:19.014760 Transaction 07fb408d5581661e888e584c92b06f546709e728e88e4218fadbd44254db3cbb rescued from peer latency cache! 2012-12-14 04:52:19.014998 Transaction 11884de24b311dbe020756b16a622e622baceca867157638e05f04673909a8bb rescued from peer latency cache! 2012-12-14 04:52:19.236951 Peer sent entire transaction 1c8de481f32a4c1dde2070c76b114b499bb12c8a5beb8bbc9b9ac7c1ec696e29 that was already received
spiccioli
|
|
|
|
gades
|
|
December 14, 2012, 02:23:46 PM |
|
Why are the units not found in the local statistics (212172,212147) http://127.0.0.1:9332/static/ and this not only in my peer! P2Pool
Graphs
Version: 9.4
Pool rate: 325GH/s (18% stale) Share difficulty: 608
Node uptime: 2.348 days Peers: 6 out, 10 in
Local rate: 437MH/s (6.6% DOA) Expected time to share: 1.66 hours
Shares: 34 total (2 orphaned, 0 dead) Efficiency: 114.2%
Payout if a block were found NOW: 0.03519026 BTC to 1A4srudzei6G1tqyWo9CgPqAoim2PKB95V. Expected after mining for 24 hours: 0.0340 BTC
Current block value: 25.43750002 BTC Expected time to block: 12.4 hours Share explorer
Best share: aabff7ec
Verified heads: 191118db e3279957 aabff7ec 95c14e91 e35b4fb0
Heads: 191118db e3279957 aabff7ec 95c14e91 e35b4fb0
Verified tails: f32048db
Tails: f32048db Blocks found in last day:
Note that blocks may have been orphaned from the P2Pool chain and so not be here. time number hash/explorer link share Payouts if a block were found NOW:
|
|
|
|
PatMan
|
|
December 14, 2012, 04:01:52 PM Last edit: December 14, 2012, 05:00:09 PM by PatMan |
|
Where in my linux p2pool directory can I look to find the human-readable version number, e.g., currently, 9.4?
run_p2pool.py --version This was while p2pool was already running normally: proofer@miner:~/src/p2pool$ run_p2pool.py --version fatal: Not a git repository (or any parent up to mount parent ) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). unknown proofer@miner:~/src/p2pool$: The p2pool directory is renamed from the forrestv-p2pool-6880123 directory that was the expansion of the 9.4 linux tarball. Git clone p2pool and copy data directory and use it All problems gone forever. Excuse my noobness, but is this for Linux or Win? And how does one get this better "Git clone p2pool" - what's the procedure? I went to the site but couldn't work it out......dur.
|
|
|
|
rav3n_pl
Legendary
Offline
Activity: 1361
Merit: 1003
Don`t panic! Organize!
|
|
December 14, 2012, 06:36:44 PM |
|
|
|
|
|
Red Emerald
|
|
December 14, 2012, 10:06:26 PM |
|
I think it's probably easiest to just leave the folder with it's original name. Doesn't that work? I seem to recall someone mentioning that a few pages back.
|
|
|
|
mdude77
Legendary
Offline
Activity: 1540
Merit: 1001
|
|
December 15, 2012, 01:40:05 AM |
|
I think it's probably easiest to just leave the folder with it's original name. Doesn't that work? I seem to recall someone mentioning that a few pages back. Not if you use a script to start it. Everytime you download a new version you have to update your script. M
|
I mine at Kano's Pool because it pays the best and is completely transparent! Come join me!
|
|
|
|