CPU usage results for pypy vs python using branch jtoomim_performance of p2pool after 21.7 hours:
Regular python: 68 minutes 3 seconds, 5.22% average
pypy: 39 minutes 20 seconds, 3.82% average
That's 42% lower CPU usage for pypy.
This is multiplicative with the jtoomim_performance benefit, so using the jtoomim_performance branch with pypy has about 65% lower CPU usage than using the head branch with regular python.
Test conditions: Core i7 4790k processor, 12 peers, 76 to 80 TH/s load (SP30s). Both nodes were run on the same server at the same time, with a local BitcoinXT bitcoind.
That's a big improvement - impressive Tying it out now.
|
|
|
How did you manage to get p2pool running with pypy btw? I tried a while back, but got strange permissions issues on install & errors when running so decided to leave it. Google & reddit searches revealed nothing, & the guide on this thread didn't work for me either. Python is a complete mystery to me..... I use Debian for my servers, so I start with: sudo apt-get install pypy pypy-dev gcc build-essential p2pool uses twisted, and twisted uses zope.interface, and in order to install either one you need setuptools, so let's start with that: wget https://bootstrap.pypa.io/ez_setup.py -O - | sudo pypy sudo rm setuptools-18.3.2.zip Then zope.interface: wget https://pypi.python.org/packages/source/z/zope.interface/zope.interface-4.1.3.tar.gz#md5=9ae3d24c0c7415deb249dd1a132f0f79 tar zxf zope.interface-4.1.3.tar.gz cd zope.interface-4.1.3/ sudo pypy setup.py install cd .. sudo rm -r zope.interface-4.1.3* Then Twisted: wget https://pypi.python.org/packages/source/T/Twisted/Twisted-15.4.0.tar.bz2 tar jxf Twisted-15.4.0.tar.bz2 cd Twisted-15.4.0 sudo pypy setup.py install cd .. sudo rm -r Twisted-15.4.0* and that should be it. Keep in mind that pypy uses a ton of RAM. You should expect about 2.5 GB of RAM per pypy-p2pool process. If you have 4 GB of RAM on your server, that will barely be enough to run bitcoind and pypy-p2pool as long as you don't have any GUIs running (no X11, no Gnome, no KDE, no XFCE). Just to confirm that this worked perfectly for me on Xubuntu 64bit. Testing stable so far Many thanks for this jtoomim! - bookmarked
|
|
|
Would this be the same for Xubuntu?
Probably. You're in a better position to answer that question than I am. Right, I'm gonna have another go. Were you logged in as root when you done this, or as a normal user? This is an excellent guide my friend thank you!
|
|
|
I use Debian for my servers, so I start with: sudo apt-get install pypy pypy-dev gcc Would this be the same for Xubuntu? Keep in mind that pypy uses a ton of RAM. You should expect about 2.5 GB of RAM per pypy-p2pool process. If you have 4 GB of RAM on your server, that will barely be enough to run bitcoind and pypy-p2pool as long as you don't have any GUIs running (no X11, no Gnome, no KDE, no XFCE).
I have 16GB RAM installed due to the amount of wallets I use, running a stripped down Xubuntu 64bit headless setup - so hopefully I should be OK.
|
|
|
The main branch only includes the BIP101 change and the payout_address web interface change. The performance modification has not been merged into the main branch yet. If you want to test out the performance improvements, you have to use the jtoomim_performance branch, which forrestv is currently testing out. https://github.com/p2pool/p2pool/tree/jtoomim_performancegit pull git checkout jtoomim_performance Edit/note: if you use pypy instead of regular python to run p2pool, the performance benefit is likely to be greater than 40%, since most of the rest of the slowdowns that I've seen would be amenable to pypy acceleration, but the problem I fixed was not. I may do some benchmarks to see if this is true in a while. Nice work jtoomim! How did you manage to get p2pool running with pypy btw? I tried a while back, but got strange permissions issues on install & errors when running so decided to leave it. Google & reddit searches revealed nothing, & the guide on this thread didn't work for me either. Python is a complete mystery to me..... Any help/guidance would be very much appreciated
|
|
|
So, on the windows version of p2pool where do the custom UI files for :9332/static go?
I've not used doze for p2pool for quite a while, but as far as I can remember the process is the same: Backup your webstatic folder Copy/replace all files into it Refresh - I don't remember having to restart p2pool, but you might need to clear the cache. Edit: **post gone**
|
|
|
I'd send you mine - but the wallet won't sync......
|
|
|
Yup, same source as I used. I did notice your out of date ssl, but apart from that, the only difference I can see is that you're using 32bit. All my systems are 64bit - & none of the PRO wallets work on them. I don't have a 32 bit system to try the wallet out on, so I've dropped the coin. Thanks anyway
|
|
|
@p3yot33at3r
I have a different setup:
client version: v0.10.1.20edd86f-dirty-redgranite OpenSSL version: OpenSSL 1.0.1f 6.Jan 2014 Berkeley DB version: Berkeley DB 5.1.29: (October 25, 2011)
It's relatively fresh compiled. Could be the client version.
Hope this information could help!
Hey deadlock1, Both my doze & Nix wallets are were the latest versions, nix were compiled from latest git source using the recommended dependencies (several times), doze was from the download link at proto.uno. What OS are you using & where did you get that version from? Thanks for taking the time to check - it's more than dev did
|
|
|
Or use different data directories with different ports for each wallet.....
|
|
|
Wooooohoooooooo got my first p2pool payment today
On your own node? You got it sorted? No not yet need to send you a pm lol Got your PM - I'll take a look shortly & let you know
|
|
|
Wooooohoooooooo got my first p2pool payment today
On your own node? You got it sorted?
|
|
|
I check this thread from time to time and am amazed at how many complaints I see! People, point your machines somewhere else. The only reason people continue to mine at this pool is greed and self delusion. They like to see daily payments and they like to be part of "one of the biggest pools", but this pool is bad for bitcoin and ultimately bad for all of its users that are not Bitmain. Yet people continue to point hash here when there are numerous options that are better for the network (and ultimately better for all of us), and still get you paid.
Besides, nobody can point me to a good BIP101/XT pool.I can. Fire up a p2pool node using the XT client if that's your thing. Currently p2pool is sitting on over 200% 7 day luck, there's no Chinese ads, you can merge mine, no late payments, you control the pool & you'll be contributing to the Network again. Happy days
|
|
|
Is anyone here using the S7 on p2pool? If so, how are they performing? I'm interested to know if they are still using the crazy queue settings with their cgminer fork & if anyone has replaced it with the mainline cgminer yet. If bitmain lower their prices again soon, I might be tempted.....if they work OK with p2pool that is.
Performance suffers with default cgminer on p2pool. I was getting about 4.4 TH/s on p2pool and 4.6 TH/s on Eligius. Just noticed that my hashrate had fallen to <50% over time. Will be doing the cgminer upgrade. Is the version on page 627 still the one to use? I'm not aware of anyone who's tried the S5 cgminer version on an S7. You might want to check with kano or ckolivas first?
|
|
|
@ btcscot: WAIT! I think I might know what the problem is...type this into terminal & show me the results: Damn this forum keeps dropping.......
|
|
|
ok so any more ideas other than re install which i dont wanna do lol
OK, the only thing I can think of (if it's not your vps provider blocking) is that there's some crap left over from the outdated previous install. Try this: sudo apt-get update sudo apt-get upgrade sudo apt-get install aptitude sudo aptitude install python-software-properties screen git python-rrdtool python-pygame python-scipy python-twisted python-twisted-web python-imaging build-essential libglib2.0-dev libglibmm-2.4-dev python-dev libssl-dev libboost-all-dev dh-autoreconf libcurl4-openssl-dev libminiupnpc-dev ufw libtool autotools-dev autoconf automake pkg-config libprotoc8 libgtk2.0-dev libgmp-dev libmpfr-dev yasm libevent-dev
Aptitude will detect if there are any conflicting dependencies & advise you - just hit enter to agree & install what it says when/if it asks. It's a bit of a long shot, but what do you got to lose? Make sure you stop Bitcoind & p2pool before doing this, & reboot when everything is done. Then try again. ok done that now getting this in bitcoind 2015-10-01 15:48:07 connect() to 84.118.73.120:8333 failed after select(): No route to host (113) Did you reboot? PM me your bitcoind conf file details dude.....
|
|
|
ok so any more ideas other than re install which i dont wanna do lol
OK, the only thing I can think of (if it's not your vps provider blocking) is that there's some crap left over from the outdated previous install. Try this: sudo apt-get update sudo apt-get upgrade sudo apt-get install aptitude sudo aptitude install python-software-properties screen git python-rrdtool python-pygame python-scipy python-twisted python-twisted-web python-imaging build-essential libglib2.0-dev libglibmm-2.4-dev python-dev libssl-dev libboost-all-dev dh-autoreconf libcurl4-openssl-dev libminiupnpc-dev ufw libtool autotools-dev autoconf automake pkg-config libprotoc8 libgtk2.0-dev libgmp-dev libmpfr-dev yasm libevent-dev
Aptitude will detect if there are any conflicting dependencies & advise you - just hit enter to agree & install what it says when/if it asks. It's a bit of a long shot, but what do you got to lose? Make sure you stop Bitcoind & p2pool before doing this, & reboot when everything is done. Then try again.
|
|
|
I want to mine it, but it's impossible with the connection problem. Ok, p3yot33at3r, let's go into the details. Which version of prototanium wallet are you using and which operating system? I prefer compiling my wallets for myself, it's easy if any time successfully done and virus-free, and I also have a selfwritten key generator, where I don't need any wallets anymore. You can read about it on CCT here (I'm p3yot3 over there): https://cryptocointalk.com/topic/40178-prototanium-its-like-unobtanium-because-it-is-not-a-new-coin-a-new-way-to-use-an-existing-coins-sidechain/page-3I'm too lazy to type it all out again...... Sorry, I shouldn't be so lazy....... Error logs & git report here: https://github.com/thegreatoldone/Prototanium/issues/2Linux 64bit wallet version & info: "version" : 100102, "protocolversion" : 70002, "walletversion" : 60000, "balance" : 0.00000000, "blocks" : 142175, "timeoffset" : 0, "connections" : 0, "proxy" : "", "difficulty" : 123918.80204276, "testnet" : false, "keypoololdest" : 1443611605, "keypoolsize" : 101, "paytxfee" : 0.00000000, "relayfee" : 0.00001000, "errors" : ""
Win7 64bit qt wallet info: Ubuntu 64bit mining wallet: 2015-10-01 14:57:44.906979 > raise Error_for_code(resp['error']['code'])(resp['error']['message'], resp['error'].get('data', None)) 2015-10-01 14:57:44.907011 > p2pool.util.jsonrpc.NarrowError: -9 Prototanium is not connected!
More debug logs: 2015-10-01 13:57:19 socket recv error Connection reset by peer (104) 2015-10-01 13:57:49 socket recv error Connection reset by peer (104) 2015-10-01 13:58:20 socket recv error Connection reset by peer (104) 2015-10-01 13:58:50 socket recv error Connection reset by peer (104) 2015-10-01 13:59:21 socket recv error Connection reset by peer (104) 2015-10-01 13:59:52 socket recv error Connection reset by peer (104) 2015-10-01 14:00:22 socket recv error Connection reset by peer (104) 2015-10-01 14:00:53 socket recv error Connection reset by peer (104) 2015-10-01 14:01:23 socket recv error Connection reset by peer (104) 2015-10-01 14:01:54 socket recv error Connection reset by peer (104) 2015-10-01 14:02:24 socket recv error Connection reset by peer (104) 2015-10-01 14:02:55 socket recv error Connection reset by peer (104) 2015-10-01 14:03:26 socket recv error Connection reset by peer (104) 2015-10-01 14:03:56 socket recv error Connection reset by peer (104) 2015-10-01 14:04:27 socket recv error Connection reset by peer (104) 2015-10-01 14:04:58 socket recv error Connection reset by peer (104) 2015-10-01 14:05:28 socket recv error Connection reset by peer (104) 2015-10-01 14:05:59 socket recv error Connection reset by peer (104) 2015-10-01 14:06:25 socket recv error Connection reset by peer (104) 2015-10-01 14:06:29 socket recv error Connection reset by peer (104) 2015-10-01 14:07:00 socket recv error Connection reset by peer (104) 2015-10-01 14:07:31 socket recv error Connection reset by peer (104) 2015-10-01 14:08:01 socket recv error Connection reset by peer (104) I've reindexed, recompiled, redowloaded, rescanned, rebooted etc multiple times. Using "addnode=" results in 0 connections & 60-100% cpu, while "connect=" & "bind=" have zero affect. I've tried every possible conf configuration with both self compiled & pre-compiled binaries - no difference - connections are sporadic & very short lived no matter what wallet I use in any country. I'm all for suggestions
|
|
|
Well I'm not going back to ghash.io. There are worse things in life than empty blocks.
Not concerning the Bitcoin network there isn't. but of course - ghash isn't a plausible option Can't fault kano's pool tbh - for a centralized pool it's top notch in all departments.
|
|
|
All good there too - version is current.
|
|
|
|