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

Quote from: phelix on August 29, 2014, 12:34:27 AM

Quote from: phelix on August 26, 2014, 12:35:47 PM

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.