In all fairness, the huge memory use is not an issue for me and is a price worth paying for increased performance - which so far is the case. My DOA rate is lower so far, my latency is also lowering gradually & my recorded hash rate is slightly higher. So far so good.
It also shows how truly terrible & slow the standard python is for p2pool........
what version of bitcoin core are You running? The latest: 0.9.4 My DOA rate has halved using pypy since I installed it - it was ~3-5%, but is now ~0.5-2.5% so I'm a happy hippy  Are you merge mining? My DOA sky rockets when merge mining. Plus, doesn't seem to be worth the effort as it's basically soloing, might as well gamble more and solo for BTC. Yeah, merge mining 7 coins in total. Your BTC DOA rate shouldn't change when you're merge mining - sounds like it's not setup right. |
|
|
|
In all fairness, the huge memory use is not an issue for me and is a price worth paying for increased performance - which so far is the case. My DOA rate is lower so far, my latency is also lowering gradually & my recorded hash rate is slightly higher. So far so good.
It also shows how truly terrible & slow the standard python is for p2pool........
what version of bitcoin core are You running? The latest: 0.9.4 My DOA rate has halved using pypy since I installed it - it was ~3-5%, but is now ~0.5-2.5% so I'm a happy hippy |
|
|
|
Anyone else having trouble running the latest binary for Linux with p2pool? Ever since I upgraded to the latest version I've been unable to get p2pool to connect on port 9999: 2015-01-16 16:38:13.821624 p2pool (version 81fc6c5-dirty) 2015-01-16 16:38:13.821724 2015-01-16 16:38:13.821780 Testing bitcoind RPC connection to ' http://127.0.0.1:9998/' with username 'IYFTechDRK'... 2015-01-16 16:38:13.850612 ...success! 2015-01-16 16:38:13.850710 Current block hash: 5f2afca31990cbc9c8be1722088daafeac266253c55a1e7f06a47 2015-01-16 16:38:13.850753 Current block height: 204176 2015-01-16 16:38:13.850777 2015-01-16 16:38:13.850815 Testing bitcoind P2P connection to '127.0.0.1:9999'... 2015-01-16 16:38:18.851266 ...taking a while. Common reasons for this include all of bitcoind's connection slots being used... Cheers. Rolled back to the previous version & everything is working again - so it would seem that the latest binary is broken with p2pool? Anyone?  Its better to ask questions like this on Darkcointalk. Or raise it as an issue on Jira. I think there is a thread over there covering this issue. Vertoe is investigating I think. I posted this on Darkcoin forum for you  There's no tech support for Darkcoin here, only buy/sell BS I'm afraid......... Thanks dude  |
|
|
|
|
In all fairness, the huge memory use is not an issue for me and is a price worth paying for increased performance - which so far is the case. My DOA rate is lower so far, my latency is also lowering gradually & my recorded hash rate is slightly higher. So far so good.
It also shows how truly terrible & slow the standard python is for p2pool........
|
|
|
|
Perfect, that's what I needed - thanks See if you can spot where I changed over to pypy:.........  I'm running 16GB Ram, so it's OK. I'll see how it fares like this for a while |
|
|
|
Right, thanks. I'll just roll with the older binary....... |
|
|
|
Anyone else having trouble running the latest binary for Linux with p2pool? Ever since I upgraded to the latest version I've been unable to get p2pool to connect on port 9999: 2015-01-16 16:38:13.821624 p2pool (version 81fc6c5-dirty) 2015-01-16 16:38:13.821724 2015-01-16 16:38:13.821780 Testing bitcoind RPC connection to ' http://127.0.0.1:9998/' with username 'IYFTechDRK'... 2015-01-16 16:38:13.850612 ...success! 2015-01-16 16:38:13.850710 Current block hash: 5f2afca31990cbc9c8be1722088daafeac266253c55a1e7f06a47 2015-01-16 16:38:13.850753 Current block height: 204176 2015-01-16 16:38:13.850777 2015-01-16 16:38:13.850815 Testing bitcoind P2P connection to '127.0.0.1:9999'... 2015-01-16 16:38:18.851266 ...taking a while. Common reasons for this include all of bitcoind's connection slots being used... Cheers. Rolled back to the previous version & everything is working again - so it would seem that the latest binary is broken with p2pool? Anyone? Latest binary is working fine @ Suprnova here, are you running on linux ? Do a netstat -lna to see if the daemon is actually listening on the port. Yeah, Xubuntu 64bit to be precise. I even tried adding "listen=1" to the conf file - no difference. Its better to ask questions like this on Darkcointalk. Or raise it as an issue on Jira. I think there is a thread over there covering this issue. Vertoe is investigating I think.
I don't have an account on darktalk - & wtf is Jira?  Excuse my ignorance  |
|
|
|
....(memory usage went up too from 500MB+ to 1500MB+)...
Seriously!? 3 x more memory? When I played with pypy, I got similar results. I concluded the initial efficiency was simply the number of peers going down. The system python libraries appeared to be c-optimized though. If the libraries are not compiled, you may see more improvement. Just tried pypy.. and wow.. the RAM usage is ... just wow. But it really does load faster. Start up p2pool on python and on pypy and you can really see the increase in speed in loading p2pool. Less DOA too and registered hashrate is faster, but even with matt's relay, the getblock latency increased (tested for around 16+ hours). Can we just rm all the .pyc files and will pypy be able run p2pool? Or is there something else we have to do? What's the command for running p2pool with pypy? |
|
|
|
Anyone else having trouble running the latest binary for Linux with p2pool? Ever since I upgraded to the latest version I've been unable to get p2pool to connect on port 9999: 2015-01-16 16:38:13.821624 p2pool (version 81fc6c5-dirty) 2015-01-16 16:38:13.821724 2015-01-16 16:38:13.821780 Testing bitcoind RPC connection to ' http://127.0.0.1:9998/' with username 'IYFTechDRK'... 2015-01-16 16:38:13.850612 ...success! 2015-01-16 16:38:13.850710 Current block hash: 5f2afca31990cbc9c8be1722088daafeac266253c55a1e7f06a47 2015-01-16 16:38:13.850753 Current block height: 204176 2015-01-16 16:38:13.850777 2015-01-16 16:38:13.850815 Testing bitcoind P2P connection to '127.0.0.1:9999'... 2015-01-16 16:38:18.851266 ...taking a while. Common reasons for this include all of bitcoind's connection slots being used... Cheers. Rolled back to the previous version & everything is working again - so it would seem that the latest binary is broken with p2pool? Anyone? |
|
|
|
Anyone else having trouble running the latest binary for Linux with p2pool? Ever since I upgraded to the latest version I've been unable to get p2pool to connect on port 9999: 2015-01-16 16:38:13.821624 p2pool (version 81fc6c5-dirty) 2015-01-16 16:38:13.821724 2015-01-16 16:38:13.821780 Testing bitcoind RPC connection to ' http://127.0.0.1:9998/' with username 'IYFTechDRK'... 2015-01-16 16:38:13.850612 ...success! 2015-01-16 16:38:13.850710 Current block hash: 5f2afca31990cbc9c8be1722088daafeac266253c55a1e7f06a47 2015-01-16 16:38:13.850753 Current block height: 204176 2015-01-16 16:38:13.850777 2015-01-16 16:38:13.850815 Testing bitcoind P2P connection to '127.0.0.1:9999'... 2015-01-16 16:38:18.851266 ...taking a while. Common reasons for this include all of bitcoind's connection slots being used... Cheers. |
|
|
|
I presume he means don't set it at the miner? I never set it with p2pool as I find p2pool manages it all very nicely Exactly. Sorry, I've been AFK trying to coax a dead S5 into life again....... Any luck? |
|
|
|
I presume he means don't set it at the miner? I never set it with p2pool as I find p2pool manages it all very nicely |
|
|
|
|
These contraptions were bulky, inefficient & expensive when they came out ages ago - so now they're old, bulky, inefficient & expensive contraptions........
|
|
|
|
Thanks for that info...
What pool would you recommend to someone that is based in the UK... currently using btc china.... its ok but I feel getting one closer to home would give better results?
thanks
Check this link to find your nearest node with the lowest latency: http://nodes.p2pool.co/Or you can try my node & see how you get on - it's a zero fee node, I'm also in the UK - details in my sig |
|
|
|
so really unless you have anything like 30-40 T/H's + Its best to stick as part of a team... or expect to wait a rather long time!!!
With p2pool you are working as a team, all nodes are connected. Have a read of the p2pool thread - there's all the info you need there |
|
|
|
if i wanna build a coin's pool , what should i do and what i needs to have can anyone tell me please
thanks
Download p2pool. Run it |
|
|
|
Thank you for your detailed response, forget me for being blonde but how much would a share be worth.
Thanks
That depends on the difficulty of the accepted share. |
|
|
|
Similar, but it was a handshake error every 30 seconds, or thereabouts. I would attribute the handshake error to the ports they were using. They hammered me for about 6 hours though. Port was 9333. |
|
|
|
On January 11th, 2013 our friend and Demand Progress co-founder Aaron Swartz took his own life. Aaron meant so much to an untold number of people whom he’d touched as an activist, writer, technologist, and loved one. The act took place while he was under indictment — senselessly with up to 50 years in prison being held over his head — for allegedly downloading too many articles from the JSTOR academic cataloging service, using MIT’s open network. As are so many, this case was built on a tenuous legal foundation, and so the prosecutors bullied Aaron to try to compel him to admit his guilt and accept a plea deal. Aaron refused. http://www.takepart.com/internets-own-boy Never forgotten. |
|
|
|
|
Show Posts
