Quote from: kgb2mining on August 30, 2014, 01:23:54 PM

Quote from: mdude77 on August 30, 2014, 12:59:13 PM

Quote from: pmorris on August 30, 2014, 11:38:38 AM

Quote from: PatMan on August 29, 2014, 11:45:07 PM

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

Basic question but do we know why some hardware isn't working well with p2pool?

I assume the hardware is driven by the same mining software like cgminer? Which is using the same protocols to talk to p2pool (stratum?) as GHash.

So is it something to do with polling frequency / latency that is p2pools fault or what?

From what I've observed with my S2, it's not capable of restarting work every 30 seconds like p2pool requires.

M

I'll second that thought. It's the 30-second work restart that is the problem. Along with trying to figure out a way to better deal with the larger per-share diff for small miners, this has been one of the largest issues needing to be fixed. However, I'm not sure where the solution lies if it's on the p2pool side, or more on the manufacturers/hardware. Someone who's been around longer might have a more accurate explanation.

Fault lies on both sides. The design of p2pool requires that the restart period be pretty brief. Remember the restart is issued when a share is found on the alt chain, and the target is finding a share every 30 seconds. To make that period longer means the difficulty has to be higher. Want 60 seconds? Think 24million share difficulty.

(I think there's something wrong with this math ... because if you scale it up to 10 minutes, the BTC block time, you should get the BTC difficulty.)

The ASIC manufacturers have no incentive to make their hardware compatible with p2pool, because it's a niche pool. All they care is that it works with the main pools.

M