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

phelix

legendary

Activity: 1708

Merit: 1020

Quote from: jedimstr on August 30, 2014, 05:12:49 AM

Any update on the Namecoin merged mining issues? I still have my Namecoin-qt down and continuing to MM with Devcoin and Ixcoin for now.
Even worse, I'm doing this on a Mac so they don't have updated QT wallets yet so I'm back a few versions.

With the latest improvements (https://github.com/namecoin/namecoin) the client can deal even with the extreme load the network has been experiencing recently (waves of 36MB of hundreds huge TXs in minutes, legit TXs though). We are still running some tests and working on binaries.

jedimstr

hero member

Activity: 798

Merit: 1000

Any update on the Namecoin merged mining issues? I still have my Namecoin-qt down and continuing to MM with Devcoin and Ixcoin for now.
Even worse, I'm doing this on a Mac so they don't have updated QT wallets yet so I'm back a few versions.

EErik

newbie

Activity: 26

Merit: 0

but hey guys what's going on? in the last 20 days p2p lost about 70 out of 250 active users / addesses (although the hashrate scores 1ph more), share diff of the pool is very high for those who do not have a farm, I personally with 3 th / s i have not done a good share in the last 20 hours ... there is no way of remodulating the share diff of p2p so that it is not so difficult for small-scale miners have a decent payout and a little more stable? ok accept the variance I can tolerate, but it seems clear that many users they are leaving the pool

E

coinme.info

sr. member

Activity: 297

Merit: 250

Quote from: CartmanSPC on August 29, 2014, 10:33:38 PM

Quote from: coinme.info on August 29, 2014, 09:36:58 PM

Found I had to install the 32bit versions as there is no python win32 api wmi wrapper for 64bit and it won't install to the 64bit python dir.
Found this out on a 2008 server so just did plain 32bit python install as per your readme.

You can get the 64 bit version to work but it's more effort than it's worth. I just do 32 bit as well.

Good to know I wasn't overlooking something simple.

All it would need is for that python win32 api wmi wrapper to be updated to 64bit as all the other requirements have 64bit versions now.

GBT latency seems to be hovering around double the latency of the 13.4 version with the java relay.

Will run up 13.4 on the 2008 server with the java relay and compare the two overnight.

CartmanSPC

legendary

Activity: 1270

Merit: 1000

Quote from: coinme.info on August 29, 2014, 09:36:58 PM

Found I had to install the 32bit versions as there is no python win32 api wmi wrapper for 64bit and it won't install to the 64bit python dir.
Found this out on a 2008 server so just did plain 32bit python install as per your readme.

You can get the 64 bit version to work but it's more effort than it's worth. I just do 32 bit as well.

coinme.info

sr. member

Activity: 297

Merit: 250

Quote from: Matt Corallo on August 29, 2014, 08:25:51 PM

Quote from: coinme.info on August 29, 2014, 06:50:26 PM

Quote from: PatMan on August 29, 2014, 04:01:16 PM

Hey guys, any first impressions on Matts fork - how's it running? Well pleased it's in python too.....

Doesn't seem to work on a Windows Server 2012 R2.

Freshly installed all the requirements and I can run P2Pool ok using Matts source from Github including merge mining.

However once I add the --relay-network public.us-west.relay.mattcorallo.com to the startup I get this.

I took out the merged mining stuff as well just in case and ran with just plain jane BTC p2pool, same thing.

Any ideas?

Back to using 13.4 precompiled from forrestv with the java relay which works well BTW.

Strange, that flag is explicitly stated in the python docs...can you try the latest push?

Hi Matt

Looks like the latest update you made has fixed it.

Tried it first with just BTC and then with merged mining options added to start up.

Can see the connection on network stats as well.

Image PID Address Send (B/sec) Receive (B/sec) Total (B/sec)
python.exe 3500 rn-sea1.relay.mattcorallo.com 0 423 423

Whatever you changed made the web pages load at normal speed as well.
The were very slow with the previous sources.

I need to run it for while to see if the GBT latency can equal or better the 13.4 version with the java as it was was 100ms higher in the previous try.

FYI running:
Python 2.7.8
Twisted: 14.0.0
Zope.Interface: 4.1.1
python win32 api: 219
python win32 api wmi wrapper: 1.4.9

Found I had to install the 32bit versions as there is no python win32 api wmi wrapper for 64bit and it won't install to the 64bit python dir.
Found this out on a 2008 server so just did plain 32bit python install as per your readme.

PS.. looks like GBT latency is settling in to what I was getting with 13.4 and java.

:-)

Matt Corallo

hero member

Activity: 755

Merit: 515

Quote from: coinme.info on August 29, 2014, 06:50:26 PM

Quote from: PatMan on August 29, 2014, 04:01:16 PM

Hey guys, any first impressions on Matts fork - how's it running? Well pleased it's in python too.....

Doesn't seem to work on a Windows Server 2012 R2.

Freshly installed all the requirements and I can run P2Pool ok using Matts source from Github including merge mining.

However once I add the --relay-network public.us-west.relay.mattcorallo.com to the startup I get this.

I took out the merged mining stuff as well just in case and ran with just plain jane BTC p2pool, same thing.

Any ideas?

Back to using 13.4 precompiled from forrestv with the java relay which works well BTW.

Strange, that flag is explicitly stated in the python docs...can you try the latest push?

windpath

legendary

Activity: 1258

Merit: 1027

Quote from: coinme.info on August 29, 2014, 06:50:26 PM

Quote from: PatMan on August 29, 2014, 04:01:16 PM

Hey guys, any first impressions on Matts fork - how's it running? Well pleased it's in python too.....

Doesn't seem to work on a Windows Server 2012 R2.

Freshly installed all the requirements and I can run P2Pool ok using Matts source from Github including merge mining.

However once I add the --relay-network public.us-west.relay.mattcorallo.com to the startup I get this.

[IMG ]https://i.imgur.com/fFysLTL.jpg[/img]

I took out the merged mining stuff as well just in case and ran with just plain jane BTC p2pool, same thing.

Any ideas?

Back to using 13.4 precompiled from forrestv with the java relay which works well BTW.

So far its running well on my local Mac, 1 share found with good luck.

Have not moved it to the production node yet, however production node runs Ubuntu and Matt maintains the PPA so I imagine no problems...

coinme.info

sr. member

Activity: 297

Merit: 250

Quote from: PatMan on August 29, 2014, 04:01:16 PM

Hey guys, any first impressions on Matts fork - how's it running? Well pleased it's in python too.....

Doesn't seem to work on a Windows Server 2012 R2.

Freshly installed all the requirements and I can run P2Pool ok using Matts source from Github including merge mining.

However once I add the --relay-network public.us-west.relay.mattcorallo.com to the startup I get this.

I took out the merged mining stuff as well just in case and ran with just plain jane BTC p2pool, same thing.

Any ideas?

Back to using 13.4 precompiled from forrestv with the java relay which works well BTW.

PatMan

hero member

Activity: 924

Merit: 1000

Watch out for the "Neg-Rep-Dogie-Police".....

Looks like the new Tube miners can be added to the "not compatible" list of miners....... Angry

Apparently, they only work with ghash Huh

I absolutely definitely won't be getting one of those then...... Cheesy

phelix

legendary

Activity: 1708

Merit: 1020

Quote from: jonnybravo0311 on August 29, 2014, 01:51:34 PM

Quote from: phelix on August 28, 2014, 07:34:27 PM

Quote from: phelix on August 26, 2014, 07:35:47 AM

How often does p2pool query namecoind getblockaux? I would like to make sure the namecoind internal recalculation time step makes sense.

Can anyone answer this for phelix? I haven't been able to dig through the code thoroughly to find any polling time. You can start in work.py to see the calls to get the merged work (around line 62):

Code:

       # MERGED WORK

        self.merged_work = variable.Variable({})

        @defer.inlineCallbacks
        def set_merged_work(merged_url, merged_userpass):
            merged_proxy = jsonrpc.HTTPProxy(merged_url, dict(Authorization='Basic ' + base64.b64encode(merged_userpass)))
            while self.running:
                auxblock = yield deferral.retry('Error while calling merged getauxblock on %s:' % (merged_url,), 30)(merged_proxy.rpc_getauxblock)()
                self.merged_work.set(math.merge_dicts(self.merged_work.value, {auxblock['chainid']: dict(
                    hash=int(auxblock['hash'], 16),
                    target='p2pool' if auxblock['target'] == 'p2pool' else pack.IntType(256).unpack(auxblock['target'].decode('hex')),
                    merged_proxy=merged_proxy,
                )}))
                yield deferral.sleep(1)
        for merged_url, merged_userpass in merged_urls:
            set_merged_work(merged_url, merged_userpass)

        @self.merged_work.changed.watch
        def _(new_merged_work):
            print 'Got new merged mining work!'

Thanks for pointing me to the right place. Looks like it is sleeping one seconds between queries. From some other part in the code it seems the timeout is 5 seconds and it will retry up to a 30 times. OK.

windpath

legendary

Activity: 1258

Merit: 1027

Quote from: Matt Corallo on August 29, 2014, 12:35:45 PM

Quote from: windpath on August 29, 2014, 08:27:04 AM

Quote from: Matt Corallo on August 29, 2014, 06:45:03 AM

Check out https://github.com/TheBlueMatt/p2pool. Once I get some testing I'll pull request that and see if I can wake forrest from his drug-induced slumber.

...
How can I verify p2pool has connected to the relay network?

Remove the addnode and run p2pool with --relay-network public.YOUR_REGION.relay.mattcorallo.com

Thanks Matt!

Code:

Initializing work...
RELAY NETWORK: Connected to relay node with protocol version prioritized panther
RELAY NETWORK: Connected to bitcoind with protocol version 70002
RELAY NETWORK: Finished connect handshake with bitcoind
     ...success!

PatMan

hero member

Activity: 924

Merit: 1000

Watch out for the "Neg-Rep-Dogie-Police".....

Hey guys, any first impressions on Matts fork - how's it running? Well pleased it's in python too.....

kgb2mining

member

Activity: 112

Merit: 10

Quote from: jonnybravo0311 on August 29, 2014, 02:58:16 PM

Quote from: kgb2mining on August 29, 2014, 02:50:02 PM

Stupid question - is it possible to setup a custom list of outgoing peer nods to talk to? I've got the default 6, but I'm wondering if I should start tinkering with adding more. There's probably a bunch of nice close fast nodes I could add in.

When you start your node, use --p2pool-node argument. For example:

Code:

./run_p2pool.py --p2pool-node 54.235.94.19:9333

By the way, that's windpath's node (located in VA).

Thanks...

Is there a way to add multiples? Just string them together on the commandline, or is there a simpler way maybe to put them in a file and read it in on startup?

jonnybravo0311

legendary

Activity: 1344

Merit: 1024

Mine at Jonny's Pool

Quote from: kgb2mining on August 29, 2014, 02:50:02 PM

Stupid question - is it possible to setup a custom list of outgoing peer nods to talk to? I've got the default 6, but I'm wondering if I should start tinkering with adding more. There's probably a bunch of nice close fast nodes I could add in.

When you start your node, use --p2pool-node argument. For example:

Code:

./run_p2pool.py --p2pool-node 54.235.94.19:9333

By the way, that's windpath's node (located in VA).

kgb2mining

member

Activity: 112

Merit: 10

Stupid question - is it possible to setup a custom list of outgoing peer nods to talk to? I've got the default 6, but I'm wondering if I should start tinkering with adding more. There's probably a bunch of nice close fast nodes I could add in.

kgb2mining

member

Activity: 112

Merit: 10

Quote from: bryonp on August 29, 2014, 01:58:43 PM

THANK YOU... that did it... will see what happens...

Cool, glad it worked.

It seems to be OK running on my node so far, let us know how it looks for you.

bryonp

member

Activity: 85

Merit: 10

Quote from: kgb2mining on August 29, 2014, 01:47:02 PM

Quote from: bryonp on August 29, 2014, 01:17:40 PM

all I get with this is
unrecognized argument --relay-network
Huh

any advise?

Did you pull down Matt's full p2pool git repo and use that instead of the original source from forrestv? If not try that. If no, not sure.

THANK YOU... that did it... will see what happens...

jonnybravo0311

legendary

Activity: 1344

Merit: 1024

Mine at Jonny's Pool

Quote from: phelix on August 28, 2014, 07:34:27 PM

Quote from: phelix on August 26, 2014, 07:35:47 AM

How often does p2pool query namecoind getblockaux? I would like to make sure the namecoind internal recalculation time step makes sense.

Can anyone answer this for phelix? I haven't been able to dig through the code thoroughly to find any polling time. You can start in work.py to see the calls to get the merged work (around line 62):

Code:

# MERGED WORK

   self.merged_work = variable.Variable({})

   @defer.inlineCallbacks
   def set_merged_work(merged_url, merged_userpass):
   merged_proxy = jsonrpc.HTTPProxy(merged_url, dict(Authorization='Basic ' + base64.b64encode(merged_userpass)))
   while self.running:
   auxblock = yield deferral.retry('Error while calling merged getauxblock on %s:' % (merged_url,), 30)(merged_proxy.rpc_getauxblock)()
   self.merged_work.set(math.merge_dicts(self.merged_work.value, {auxblock['chainid']: dict(
   hash=int(auxblock['hash'], 16),
   target='p2pool' if auxblock['target'] == 'p2pool' else pack.IntType(256).unpack(auxblock['target'].decode('hex')),
   merged_proxy=merged_proxy,
   )}))
   yield deferral.sleep(1)
   for merged_url, merged_userpass in merged_urls:
   set_merged_work(merged_url, merged_userpass)

   @self.merged_work.changed.watch
   def _(new_merged_work):
   print 'Got new merged mining work!'

kgb2mining

member

Activity: 112

Merit: 10

Quote from: bryonp on August 29, 2014, 01:17:40 PM

all I get with this is
unrecognized argument --relay-network
Huh

any advise?

Did you pull down Matt's full p2pool git repo and use that instead of the original source from forrestv? If not try that. If no, not sure.

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