Quote from: gyverlb on March 11, 2013, 06:50:42 PM

Quote from: lenny_ on March 11, 2013, 05:58:58 PM

I think we completely misunderstand each other.
I am talking about:
my FPGA hardware doing 0.01% rejects or less on Bitminter using Stratum. Same hardware, exactly same configuration doing 15% rejects on p2pool. I tried to tweak config and got slightly better results about 10% but that's still not the main case. 15% - That's reported by miner and by p2pool stats as well.

That's much too high. I have ~2.5% rejects on all my Spartan6 (CM1 and Icarus with MPBM). I have 2.6% rejects on my GPUs (5870 and 5970 with cgminer).
So I really don't see any problem with FPGAs and P2Pool: in fact they react slightly faster than my GPUs (cgminer autotune the intensity on each one to react in 50ms).

Quote from: lenny_ on March 11, 2013, 05:58:58 PM

That's wasting resources, nothing else. When we invest our money and time in something, we should do it right.

They don't waste resource, a share is only rejected if it both arrives too late and doesn't solve a block so there's no,zero,0 income wasted by these rejects. I repeat: rejects don't reduce the pool's income.

Quote from: lenny_ on March 11, 2013, 05:58:58 PM

FPGAs just react too slow to change nonce every couple of seconds

Now that's mixing your particular configuration which is clearly not optimized for p2pool and plain FUD (since when the target is a couple of seconds?).

Quote from: lenny_ on March 11, 2013, 05:58:58 PM

, to top of that add remote node's bitcoind latency + network latency + time to prepare getwork etc... This is just not working for LP= 10s, it's a disaster.

Nope, it isn't a disaster: I earned more with p2pool in 6 months than I would have on a 100% PPS pool since I started (I keep track of each and every payment and compare it to my theoretical income on a no fee PPS pool).

Quote from: lenny_ on March 11, 2013, 05:58:58 PM

No one is mining of remote p2pool nodes as it will just not work as it is right now.

Probably depends on the actual node and who connects to it: some have better connectivity than others. I used to mine on one of my rented VPS servers with a 45ms round-trip time with my miners and it worked OK (it was around 98% efficiency IIRC).

Quote from: lenny_ on March 11, 2013, 05:58:58 PM

If you guys are saying there is no solution for that - so beware, because one day p2pool will die.

I think p2pool is for geeks who like to setup and tune everything themselves. When you can host a node properly (for me this means locally on a host with a good CPU, 2GB RAM on a Linux server dedicated to bitcoind+p2pool, a SSD to store bitcoind's data and with a good QoS setup so that both bitcoind and p2pool don't suffer from other traffic on your WAN connection) and configure a backup pool it's arguably the most reliable and profitable option.

It's not for everyone, but if you are a serious miner and have the network connection and hardware available it's simply the best solution. From what you wrote there are surprising latencies in your setup: it probably isn't for you.

Can you please share your settings with me? cgminer is able to get similar results?