gyverlb
|
|
September 23, 2013, 04:50:29 PM |
|
I will give it a try. Is ur guide the most uptodate?
For tuning probably: at least I'm not aware of any other verified information that would be relevant. For the basic installation this thread's first post and the wiki page should have you covered (it assumes basic sysadmin skills).
|
|
|
|
HellDiverUK
|
|
September 23, 2013, 05:07:48 PM |
|
When was that? Before or after the last protocol fork (which made it efficient with most ASICs) which happened in July? If it was after the fork it's surprising as it should have solved these problems.
It was running 13.3. I'll maybe have another go with it sometime, perhaps there was something strange with my install, or I missed something. I'm pretty sure I did everything I should have, though. I'm rejiggering my workstation in the next few days, including a fresh install, so I'll see if I can have another go. Still, all that said, I'm still getting far better returns from a larger pool than I did on p2pool.
|
|
|
|
centove
|
|
September 23, 2013, 05:41:13 PM |
|
When was that? Before or after the last protocol fork (which made it efficient with most ASICs) which happened in July? If it was after the fork it's surprising as it should have solved these problems.
It was running 13.3. I'll maybe have another go with it sometime, perhaps there was something strange with my install, or I missed something. I'm pretty sure I did everything I should have, though. I'm rejiggering my workstation in the next few days, including a fresh install, so I'll see if I can have another go. Still, all that said, I'm still getting far better returns from a larger pool than I did on p2pool. Kinda a catch 22 there... More hash rate == Quicker Block solves == lower variance. (PPLNS payout) p2pool has less total hash rate so therefore it will have higher variance which will lead to fewer people using it which leads to lower total hash rate....
|
|
|
|
gyverlb
|
|
September 23, 2013, 05:57:55 PM |
|
Kinda a catch 22 there... More hash rate == Quicker Block solves == lower variance. (PPLNS payout) p2pool has less total hash rate so therefore it will have higher variance which will lead to fewer people using it which leads to lower total hash rate....
That's not so bad. People leaving are those with the worst configurations (network issues or underpowered node), who don't have the sysadmin skills to maintain a node or who can't stand the variance (due to very low hashrates or luck misunderstanding). Regular users of p2pool are those who know how to set it up, maintain and optimize it: they build a high quality network of nodes that should outperform any centralized pool. With lots of well configured nodes broadcasting our blocks, we should have lower orphan rate. As anyone verified/quantified this by the way? Last time I studied the orphan rate for solo miners on alt-coins, I found a block collision rate that was equivalent to a 3 to 5 seconds window where a block would be orphaned. This should amount to a ~0.5% orphan rate on the bitcoin P2P network. This is over-simplified by assuming most pools use a single bitcoind to broadcast their block (some have severals or have direct connections to other "friend" pools). Is there some archive of P2Pool found blocks somewhere? Looking at the last thousand and comparing to the largest pools we should have an idea of our performance.
|
|
|
|
HellDiverUK
|
|
September 23, 2013, 06:23:45 PM |
|
I'm not sure my internet is good enough to be hosting a p2pool node, either. I'm just on 12/1Mb ADSL. It's not the quickest, and probably quite latent when other things happen, despite QoS.
|
|
|
|
ksenter
Member
Offline
Activity: 90
Merit: 10
|
|
September 23, 2013, 07:22:13 PM |
|
I havent kept up with P2pool for so long. Way back when i tried it with GPUs more than a year ago, its very resource hungry and variances were so high.
Still resource hungry, still high variance. I was really keen to use P2Pool, and ran it for several months, but to be honest it was just too much - it needed a fast machine to run it, and payouts were pretty woeful. Half of any mining profits (if I got any at all) was wasted on power to run the i3 machine needed to make P2Pool perform anywhere near well enough. I tried to run it on a Sempron dual core 2.5GHz CPU, and it struggled with a measly 5GH/s. Someone said they ran P2Pool on a Celeron 847, but I think they were huffing glue. Now I'm up to 35GH/s, I gave up on P2Pool. I get far better returns with less bother on a 'real' pool. Out of curiosity, what are your returns like? I have 30GH on p2pool, you have 35GH on a larger pool, so our results should be close. I've been on p2pool for a while now and I'm wondering if you're making enough more than me for it to be worth switching. So far in the month of September I've made 3.567564 BTC. If you're within 10% of that I'm staying because I like the idea of p2pool. If you need a different date range to compare let me know. Edit: 10% after accounting for your extra 5GH of course.
|
|
|
|
gyverlb
|
|
September 23, 2013, 08:02:46 PM |
|
I'm not sure my internet is good enough to be hosting a p2pool node, either. I'm just on 12/1Mb ADSL. It's not the quickest, and probably quite latent when other things happen, despite QoS.
12/1Mb is plenty. I have nearly the same: ~14.5/1.4Mb. I need to use QoS settings giving higher priority to the *coind and P2Pool traffic and I tuned them according to my guide.
|
|
|
|
IYFTech
|
|
September 24, 2013, 01:50:59 AM |
|
I havent kept up with P2pool for so long. Way back when i tried it with GPUs more than a year ago, its very resource hungry and variances were so high.
Still resource hungry, still high variance. I was really keen to use P2Pool, and ran it for several months, but to be honest it was just too much - it needed a fast machine to run it, and payouts were pretty woeful. Half of any mining profits (if I got any at all) was wasted on power to run the i3 machine needed to make P2Pool perform anywhere near well enough. I tried to run it on a Sempron dual core 2.5GHz CPU, and it struggled with a measly 5GH/s. Someone said they ran P2Pool on a Celeron 847, but I think they were huffing glue. Now I'm up to 35GH/s, I gave up on P2Pool. I get far better returns with less bother on a 'real' pool. It's all in the setup my man. I gave up using high powered & expensive gear on p2pool, it's simply not worth it due to the limit of mining gear that actually works with it, unless you got an ASIC & are knowledgeable & bothered enough to faff around with it to make it work. I opted for energy efficiency over performance with p2pool & it's now worth while actually using it. I use a Sempron 145 with unlocked core (making it a 45w dual core Athlon II X2 OC'd @ 3.4!!) with 8Gig 1600 RAM, a separate SSD for the 6 merged mined coins data & a Gold 850W PSU running Xubuntu 64bit 12.04. My miner is an old Acer One Netbook (Xununtu) running 40 usb's (it gives the lowest reject/hw error rate of all my equipment: <1%) All this goes through a UPS that shows a measly 225 watts draw. That's less than the average desktop PC. I also gave up faffing around with the settings, most of the suggestions in g's guide actually made things worse anyway (after all, it's a guide, not a bible), but everybody's setup is different of course - but my rig likes things standard. All this talk of having to be some sort of geeky administrator to get p2pool to run right makes me laugh - if a dope-head like me can do it, anyone can. I struggle with compiling stuff FFS A geek I am not, I chuff. P2pool will never be a "real" pool until the compatibility issues are sorted out. When noobs can come along, plug in & play, the pool will grow to be what it deserves to be, like every other pool has. Until then, for me anyway, it's a toy to play with - a learning process - but a fun one. it might even payout once or twice. If you're lucky .
|
|
|
|
HellDiverUK
|
|
September 24, 2013, 07:29:17 AM |
|
Out of curiosity, what are your returns like? I have 30GH on p2pool, you have 35GH on a larger pool, so our results should be close. I've been on p2pool for a while now and I'm wondering if you're making enough more than me for it to be worth switching. So far in the month of September I've made 3.567564 BTC. If you're within 10% of that I'm staying because I like the idea of p2pool. If you need a different date range to compare let me know.
With various faffing about, my average over the past 24 hours has been 31GH/s (one of my Blades was a bit sick, needed more power to stabilise it), I got BTC0.167 on EclipseMC. I've only just moved there to see how it goes. Eligius was paying out around 25 hours, and I think they pay out around 0.167 too. Taking 23 full days in September so far, that's about BTC3.841. Ignoring variance, of course. Edit: Actual figures according to EMC are 0.16704727620043 / 24 hours
|
|
|
|
HellDiverUK
|
|
September 24, 2013, 07:43:04 AM |
|
P2pool will never be a "real" pool until the compatibility issues are sorted out. When noobs can come along, plug in & play, the pool will grow to be what it deserves to be, like every other pool has. Until then, for me anyway, it's a toy to play with - a learning process - but a fun one. it might even payout once or twice. If you're lucky . Agreed. It's easy enough to set up, once you've spent 24 hours figuring it out. If there was some sort of installer, or if p2pool was just an executable that didn't need all the faffing, I think a lot more folks would run it. On the Windows end of things, all it needs is an installer that adds the bitcoin.conf files, asks a few questions, opens a few ports, job done. But, it seems linux is the main focus of bitcoin software authors, despite a huge proportion of people running Windows. It all smacks of elitism. But, hey, I'm just an IT administrator from the world of Windows, who started out in the days of NT3.51, what would I know?
|
|
|
|
paulkoan
Newbie
Offline
Activity: 43
Merit: 0
|
|
September 24, 2013, 02:07:31 PM |
|
Any ideas what might cause the below? I am git-pulled to the latest code, and I get this pretty much straight away. This is on debian unstable, with python 2.7: 2013-09-22 17:53:04.518314 Listening for workers on '' port 9332... 2013-09-22 17:53:06.970859 > Fatal error: 2013-09-22 17:53:06.970915 > Traceback (most recent call last): 2013-09-22 17:53:06.970973 > File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 488, in _startRunCallbacks 2013-09-22 17:53:06.971000 > self._runCallbacks() 2013-09-22 17:53:06.971030 > File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 575, in _runCallbacks 2013-09-22 17:53:06.971055 > current.result = callback(current.result, *args, **kw) 2013-09-22 17:53:06.971078 > File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1126, in gotResult 2013-09-22 17:53:06.971101 > _inlineCallbacks(r, g, deferred) 2013-09-22 17:53:06.971124 > File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1070, in _inlineCallbacks 2013-09-22 17:53:06.971147 > result = g.send(result) 2013-09-22 17:53:06.971169 > --- <exception caught here> --- 2013-09-22 17:53:06.971191 > File "/home/share/apps/finance/p2pool/p2pool/main.py", line 214, in main 2013-09-22 17:53:06.971213 > web_root = web.get_web_root(wb, datadir_path, bitcoind_getinfo_var) 2013-09-22 17:53:06.971235 > File "/home/share/apps/finance/p2pool/p2pool/web.py", line 374, in get_web_root 2013-09-22 17:53:06.971261 > }, hd_obj) 2013-09-22 17:53:06.971283 > File "/home/share/apps/finance/p2pool/p2pool/util/graph.py", line 129, in from_obj 2013-09-22 17:53:06.971306 > for ds_name, ds_desc in datastream_descriptions.iteritems() 2013-09-22 17:53:06.971328 > File "/home/share/apps/finance/p2pool/p2pool/util/graph.py", line 129, in <genexpr> 2013-09-22 17:53:06.971350 > for ds_name, ds_desc in datastream_descriptions.iteritems() 2013-09-22 17:53:06.971372 > File "/home/share/apps/finance/p2pool/p2pool/util/graph.py", line 127, in <genexpr> 2013-09-22 17:53:06.971394 > for dv_name, dv_desc in ds_desc.dataview_descriptions.iteritems() 2013-09-22 17:53:06.971417 > File "/home/share/apps/finance/p2pool/p2pool/util/graph.py", line 119, in get_dataview 2013-09-22 17:53:06.971440 > return DataView(dv_desc, ds_desc, dv_data['last_bin_end'], map(convert_bin, dv_data['bins'])) 2013-09-22 17:53:06.971463 > File "/home/share/apps/finance/p2pool/p2pool/util/graph.py", line 109, in convert_bin 2013-09-22 17:53:06.971485 > total, count = bin 2013-09-22 17:53:06.971506 > exceptions.TypeError: 'int' object is not iterable
|
|
|
|
ksenter
Member
Offline
Activity: 90
Merit: 10
|
|
September 24, 2013, 03:34:21 PM |
|
Out of curiosity, what are your returns like? I have 30GH on p2pool, you have 35GH on a larger pool, so our results should be close. I've been on p2pool for a while now and I'm wondering if you're making enough more than me for it to be worth switching. So far in the month of September I've made 3.567564 BTC. If you're within 10% of that I'm staying because I like the idea of p2pool. If you need a different date range to compare let me know.
With various faffing about, my average over the past 24 hours has been 31GH/s (one of my Blades was a bit sick, needed more power to stabilise it), I got BTC0.167 on EclipseMC. I've only just moved there to see how it goes. Eligius was paying out around 25 hours, and I think they pay out around 0.167 too. Taking 23 full days in September so far, that's about BTC3.841. Ignoring variance, of course. Edit: Actual figures according to EMC are 0.16704727620043 / 24 hours Thanks, that helps. I'd rather see actual earnings over the time period, it looks like you're extrapolating. But it still helps give me an idea of what the difference would be. I might actually try another pool at some point. I've been on eligius and btcguild in the past, but not eclipse. I liked the pools just fine, I just like the idea of p2pool. Anyway, I gotta stay on p2pool at least until I finish my latest changes to the android widget I'm working on.
|
|
|
|
rav3n_pl
Legendary
Offline
Activity: 1361
Merit: 1003
Don`t panic! Organize!
|
|
September 24, 2013, 07:20:09 PM |
|
Any ideas what might cause the below? I am git-pulled to the latest code, and I get this pretty much straight away. This is on debian unstable, with python 2.7: 2013-09-22 17:53:04.518314 Listening for workers on '' port 9332... 2013-09-22 17:53:06.970859 > Fatal error: (...) 2013-09-22 17:53:06.971235 > File "/home/share/apps/finance/p2pool/p2pool/web.py", line 374, in get_web_root 2013-09-22 17:53:06.971261 > }, hd_obj) (...) 2013-09-22 17:53:06.971417 > File "/home/share/apps/finance/p2pool/p2pool/util/graph.py", line 119, in get_dataview 2013-09-22 17:53:06.971440 > return DataView(dv_desc, ds_desc, dv_data['last_bin_end'], map(convert_bin, dv_data['bins'])) 2013-09-22 17:53:06.971463 > File "/home/share/apps/finance/p2pool/p2pool/util/graph.py", line 109, in convert_bin 2013-09-22 17:53:06.971485 > total, count = bin 2013-09-22 17:53:06.971506 > exceptions.TypeError: 'int' object is not iterable
It is when you open web page of your node when it is totally fresh and have no data to display in graphs.
|
|
|
|
paulkoan
Newbie
Offline
Activity: 43
Merit: 0
|
|
September 24, 2013, 09:56:56 PM |
|
Any ideas what might cause the below? I am git-pulled to the latest code, and I get this pretty much straight away. This is on debian unstable, with python 2.7: 2013-09-22 17:53:04.518314 Listening for workers on '' port 9332... 2013-09-22 17:53:06.970859 > Fatal error: (...) 2013-09-22 17:53:06.971235 > File "/home/share/apps/finance/p2pool/p2pool/web.py", line 374, in get_web_root 2013-09-22 17:53:06.971261 > }, hd_obj) (...) 2013-09-22 17:53:06.971417 > File "/home/share/apps/finance/p2pool/p2pool/util/graph.py", line 119, in get_dataview 2013-09-22 17:53:06.971440 > return DataView(dv_desc, ds_desc, dv_data['last_bin_end'], map(convert_bin, dv_data['bins'])) 2013-09-22 17:53:06.971463 > File "/home/share/apps/finance/p2pool/p2pool/util/graph.py", line 109, in convert_bin 2013-09-22 17:53:06.971485 > total, count = bin 2013-09-22 17:53:06.971506 > exceptions.TypeError: 'int' object is not iterable
It is when you open web page of your node when it is totally fresh and have no data to display in graphs. This is happening at startup - you can see the listening line. Then it immediately crashes with this error. If I change the port - in case there is a browser somewhere trying to connect before the instance is ready - I get the same crash.
|
|
|
|
rav3n_pl
Legendary
Offline
Activity: 1361
Merit: 1003
Don`t panic! Organize!
|
|
September 25, 2013, 08:05:16 AM |
|
Try clear data dir.
|
|
|
|
forrestv (OP)
|
|
September 25, 2013, 12:11:53 PM Last edit: September 25, 2013, 01:49:39 PM by forrestv |
|
Or check out the latest release if master is broken - "git checkout 13.3"
Yeah, try deleting the "data" directory in the p2pool directory.
|
1J1zegkNSbwX4smvTdoHSanUfwvXFeuV23
|
|
|
Eternity
|
|
September 25, 2013, 12:45:55 PM |
|
I am having issues to connect ?
|
|
|
|
ktbken
|
|
September 25, 2013, 03:47:39 PM |
|
I am having issues to connect ?
Not a lot of info to work with there !
|
|
|
|
zvs
Legendary
Offline
Activity: 1680
Merit: 1000
https://web.archive.org/web/*/nogleg.com
|
|
September 25, 2013, 03:56:42 PM |
|
I am having issues to connect ?
does p2pool actually start up? i would think mostly people would probably have an issue with listen=0 or so in the bitcoin.conf file
|
|
|
|
paulkoan
Newbie
Offline
Activity: 43
Merit: 0
|
|
September 26, 2013, 12:33:57 PM |
|
Try clear data dir.
Thanks buddy, nailed it.
|
|
|
|
|