[1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 715.

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Noticed a few blocks recently with coinbase payments (10 addresses) with random block sources ...
Anyone know if it is another P2Pool? Or is it just the people still mining on P2Pool who didn't update?

Blocks: 176210 (failed fork), 175998 (failed fork), 174343 (failed fork)
The blocks before that are before 1-Apr (not failed forks) so I guess that would make sense also: 172428, 172357, 172069, 171896 etc.

The address getting the largest (now failed) payments is: 1FcTuPJzdekvzTyQ5dXsnsVyT4F5G1tCjc
If it is P2Pool though, it's slightly modified
(it doesn't have the 0 BTC payment tacked on the end of all P2Pool coinbase txn's - but I wonder if it is documented anywhere what that actually is?)

bitpop

legendary

Activity: 2912

Merit: 1060

try cigwin

DeathAndTaxes

donator

Activity: 1218

Merit: 1079

Gerald Davis

So trying to setup p2pool (python source) on Windows 7.

Already have bitcoind 0.6 & p2pool 10.3 (exe) running without issue.

Installed python 2.7.3 (x64) for Windows 7
Installed Twisted 12.0.0 for python 2.7.3 Windows 7
Downloaded latest github version of p2pool:

Code:

C:\Bitcoin\p2pool-0.10.3-41>setup.py
Traceback (most recent call last):
  File "C:\Bitcoin\p2pool-0.10.3-41\setup.py", line 7, in 
    import py2exe
ImportError: No module named py2exe


C:\Bitcoin\p2pool-0.10.3-41>run_p2pool.py
Traceback (most recent call last):
  File "C:\Bitcoin\p2pool-0.10.3-41\run_p2pool.py", line 3, in  from p2pool import main
  File "C:\Bitcoin\p2pool-0.10.3-41\p2pool\main.py", line 22, in  from twisted.internet import defer, reactor, protocol, task
  File "C:\Python27\lib\site-packages\twisted\internet\defer.py", line 25, in  from twisted.python import log, failure, lockfile
  File "C:\Python27\lib\site-packages\twisted\python\log.py", line 17, in  from zope.interface import Interface
ImportError: No module named zope.interface

Any ideas?

On edit: looks like "zope.interface" is required.
http://www.lfd.uci.edu/~gohlke/pythonlibs/#zope.interface

Installing zope.interface-3.8.0.win-amd64-py2.7.‌exe got rid of the errors.

forrestv the dependencies on first page should likely be updated to reflect Bitcoind 0.6 (or 0.5.4 backport) and python "zope.interface".

twmz

hero member

Activity: 737

Merit: 500

Quote from: DeathAndTaxes on April 18, 2012, 08:37:45 AM

Quote from: camolist on April 18, 2012, 07:30:56 AM

went from 91-92% efficiency running p2pool locally (over 100 shares) to > 100 % (only 31 shares so far but just one dead) running it on a virtual server in a good datacenter

Now that is interesting.

Can you dig into the stats and see why?

I have very high efficiency with my current p2pool setup. Here are my current stats (it has been a week or two since I most recently restarted p2pool):

Code:

Shares: 896 (22 orphan, 10 dead) Stale rate: ~3.6% (2-5%) Efficiency: ~102.6% (101-104%)

I have been consistently getting approx 3.5% stale rate for the past month or so, so this is not a fluke. Here are some musings...

The hardware that p2pool and bitcoind runs on matters. I went from a VM to a fast physical machine (for just p2pool and bitcoind--no change to miners) and that dropped my stale rate by half. My assumption is that CPU speed matters more than RAM amount as long as you have enough RAM that there is no swapping. Disk performance may also matter for bitcoind.
The conventional wisdom on parameters for cgminer is not as relevant as people make it sound. For example, I do not use 1 thread per GPU. I found that to be irrelevent. My settings vary from rig to rig (my rigs are not all identical GPU hardware or even SDK/driver version). For each rig, I experimented with combinations of thread and intensity until I found the best hashrate and stale rate. In all cases, I ended up with either 2 or 3 threads per GPU and intensity setting different than what people normally seem to use.
I don't have data to back this up because I don't have a "control" to compare against, but I suspect that connected-ness of p2pool matters a lot. My node is an old node and so almost always has 40 incoming connections. With only a few hundred nodes total, that means I am hearing about new shares directly from about 20-25% of the nodes instead of hearing about new shares second or third hand.

In my experience over the past several months, it was the hardware change that made the most dramatic and instant impact. I went from "average" stale rate to "consistently 2-3% better than average" stale rate over night when I changed the hardware for my primary p2pool node.

Of course, I probably should just keep my mouth shut and enjoy my extra efficiency. If everyone improves their stale rate, my great stale rate becomes just average again

DeathAndTaxes

donator

Activity: 1218

Merit: 1079

Gerald Davis

Quote from: camolist on April 18, 2012, 07:30:56 AM

went from 91-92% efficiency running p2pool locally (over 100 shares) to > 100 % (only 31 shares so far but just one dead) running it on a virtual server in a good datacenter

Now that is interesting.

Can you dig into the stats and see why?

Most likely one of the three must have changed.
a) lower orphans (maybe because hosted instance has lower latency links to peers)?*
b) lower dead rate (maybe because the local instance was unable to keep up introducing delays)?
c) higher effective hashrate (server 0 not providing work fast enough errors in cgminer?)

* On lower orphans I wonder how much latency to peers matters. Currently IIRC nodes only pick peers based on stability (how long they have seen them) but I wonder if nodes should drop peers in favor or other peers if latency is too high and/or if peer is on an older version. In essence a more heuristic approach to picking peers.

http://50.31.2.7:9332/static/
http://50.31.2.7:9332/static/graphs.html

hope this helps someone getting high dead and orphan numbers on a copy of p2pool ran locally
[/quote]

bitpop

legendary

Activity: 2912

Merit: 1060

Python version upgrades have breaking changes and aren't necessarily updates.

DeathAndTaxes

donator

Activity: 1218

Merit: 1079

Gerald Davis

So I decided to finally switch my Win7 box from the precompiled version to the python script version so I can incorporate latest changes (and some custom ones).

Is there a guide anywhere for setting up the non exe version of p2pool with Windows 7?
Should all the historical data (charts, stats) be compatible in the switch?
Also latest python version is 3.2.3. Is p2pool not compatible w/ 3.x and that is why recommended version is 2.7.x?

bitpop

legendary

Activity: 2912

Merit: 1060

Thats why you should try my free node

Ente

legendary

Activity: 2126

Merit: 1001

Quote from: camolist on April 18, 2012, 07:30:56 AM

went from 91-92% efficiency running p2pool locally (over 100 shares) to > 100 % (only 31 shares so far but just one dead) running it on a virtual server in a good datacenter

Interesting! I wouldn't have expected this.. Nice find! Report back in a week, curious how this turns out!

Ente

camolist

hero member

Activity: 896

Merit: 1000

Quote from: camolist on April 15, 2012, 07:31:39 AM

loving p2pool. just need to either figure out why windows 7 is crashing about once a day or switch to linux soon

would it be a disadvantage to host p2pool on a server about 50ms away from the mining computer?

how much bandwidth is transferred while connected to the pool? connected locally this is not an issue at all but curious if it were to be hosted remotely

advantages i can see right away would be guaranteed static ip and perfect uptime along with a great network. could even make it a public fee free pool if bandwidth use is low enough

after looking at the errors i think the windows problem was having 4gb of ram on a board that supports 2. it's been stable for awhile since taking a piece out

went ahead and just tried this since i didn't see any comments on it

went from 91-92% efficiency running p2pool locally (over 100 shares) to > 100 % (only 31 shares so far but just one dead) running it on a virtual server in a good datacenter

http://50.31.2.7:9332/static/
http://50.31.2.7:9332/static/graphs.html

hope this helps someone getting high dead and orphan numbers on a copy of p2pool ran locally

arklan

legendary

Activity: 1778

Merit: 1008

ok, so been on p2pmining.com for a bit now - seems ot work well as i said previous. but... how do i get the payout? a block was completed, and the payment confirmed according to the website. i've tried the instant payout tab corresponding to my address, but i haven't the foggiest what to actually enteras a signature to get it to pay out. i assumed it was the provided "sign this message", like "pay-123456789" but that just returns invalid signature.

clearly, i'm some kind of ultra newb here... little help?

EDIT: ignore all that, i figured it out.

arklan

legendary

Activity: 1778

Merit: 1008

will do. thanks.

EDIT: checked it out. wow! excellent. easy as pie to set up and instantly earmed some payout. ...a very tiny amount mind, but every penny counts. er... every... uh... bit-penny?

Red Emerald

hero member

Activity: 742

Merit: 500

Quote from: arklan on April 16, 2012, 06:19:17 PM

well like i said originally, only 80mh, the payment is really basically costing more then my electricity anyway, so, oh well to the lost day. Cheesy

You should look at p2pmining.com. Its a p2pool node meant for small miners

arklan

legendary

Activity: 1778

Merit: 1008

well like i said originally, only 80mh, the payment is really basically costing more then my electricity anyway, so, oh well to the lost day. Cheesy

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

Quote from: TheHarbinger on April 16, 2012, 04:02:05 PM

Quote from: arklan on April 16, 2012, 12:06:16 PM

yea, static payment.
pool is showing 314ghash
current payout 0.0000

and no payment is listed for my address.

but now i know where to check. thanks.

With only 80Mh/s, it is very possible that you did not have any found shares in the last 24 hours. Since p2pool calculates payouts based on the number of shares in the 24 hours prior to a found block you would have a zero payout. But on the other hand, tomorrow you could find 4 shares, and be like Rick James, rich bitch! Wink

Hmm someone has an interesting idea of what rich means ...

Of course once you know that you missed a day of payment, there is of course no memory in the process of share calculation, so there is also no guarantee that you will ever get that day back ...

arklan

legendary

Activity: 1778

Merit: 1008

yea, now that i've thought about it, i realize that's likely what happened. thanks guys.

TheHarbinger

sr. member

Activity: 378

Merit: 250

Why is it so damn hot in here?

Quote from: arklan on April 16, 2012, 12:06:16 PM

yea, static payment.
pool is showing 314ghash
current payout 0.0000

and no payment is listed for my address.

but now i know where to check. thanks.

With only 80Mh/s, it is very possible that you did not have any found shares in the last 24 hours. Since p2pool calculates payouts based on the number of shares in the 24 hours prior to a found block you would have a zero payout. But on the other hand, tomorrow you could find 4 shares, and be like Rick James, rich bitch! Wink

arklan

legendary

Activity: 1778

Merit: 1008

yea, static payment.
pool is showing 314ghash
current payout 0.0000

and no payment is listed for my address.

but now i know where to check. thanks.

DeathAndTaxes

donator

Activity: 1218

Merit: 1079

Gerald Davis

Are you using a static payment address?
If the address listed here: http://p2pool.info/ (under current payouts)?
What does p2pool daemon show as "Current Payout"?
What does p2pool daemon show as pool hashrate "Pool: XX GH/s"?

arklan

legendary

Activity: 1778

Merit: 1008

that is indeed the case. i'm sure it doesn't help this isn't a dedicated miner... ok, well, i'll stopp worrying about it then. thanks.

Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 715. (Read 2591919 times)