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

[baloo_kiev]

Why does this happen?



After two days I have 10 shares and 1 orphan and 2.4% DOA? Am I doing something wrong?

I think it's just variance. If you don't find shares for a long time, your current payout starts decreasing (as your older shares become outdated).

[Boing7898]

When was the last time that P2Pool found a block?

[chanson]

Why does this happen?



After two days I have 10 shares and 1 orphan and 2.4% DOA? Am I doing something wrong?

I think it's just variance. If you don't find shares for a long time, your current payout starts decreasing (as your older shares become outdated).

I can understand that shares decrease in value as the total number of shares in the block increases (hence the overall downward sloping of the flat regions). But what explains the jumps up and down? I only have one orphan, and 9 valid shares in this block... (two found during the time plotted there). The jumps up only correspond with one found share... (the orphan was before the start of the plot).

Or are the big jumps down because someone found a very high value share?

[Carlton Banks]

the shares are only valid in the sharechain for 24 hours, the p2pool share count doesn't deduct those ones. The graph shown does. If it's any consolation, 2 days is a very short sample period. p2pool exposes you to more of the statistical variation than any other pool, but that works out in the long term, and most people are mining long term now. 

[baloo_kiev]

When was the last time that P2Pool found a block?

http://p2pool.info/ - all blocks + luck charts

[baloo_kiev]

Could someone who has AM blades grab one and mine on 78.27.191.182, ports 8353 and 8354, for about 5 minutes on each please.

First one is p2pool node worker port, second is getwork port of stratum mining proxy, which itself is directed to the same node.
I am trying to debug with some tweaks.

Thanks!

[baloo_kiev]

I can understand that shares decrease in value as the total number of shares in the block increases (hence the overall downward sloping of the flat regions). But what explains the jumps up and down? I only have one orphan, and 9 valid shares in this block... (two found during the time plotted there).

Payout system in the pool is PPLNS, which stands for pay per last N shares. Jumps down occur when one of your shares becomes so old that it is excluded from those "last N shares". Thus, not every share is actually paid. However, this works both ways! When a block is found, your payout will not drop to zero but remain the same, so you may eventually get paid several times (from several blocks) for the same share!

[Boing7898]

Is it normal for a node with 2GH/s?

[rav3n_pl]

Is it normal for a node with 2GH/s?

No. You just step on memory leak. Git pull and restart node.

[Boing7898]

Is it normal for a node with 2GH/s?

No. You just step on memory leak. Git pull and restart node.

Updated and restarted, looks better now: 300 MB of memory used.
Does it increases with the hashrate or not?

[yxxyun]

wow, the hashrate now is over 900Gh/s!

[Subo1977]

wow, the hashrate now is over 900Gh/s!

witout increase of DOA....

Whre comes it from 

[centove]

wow, the hashrate now is over 900Gh/s!

witout increase of DOA....

Whre comes it from 

Probably some more ASIC's coming on line.. Difficulty is up though.. Though it looks like that may be slowing down as well. Luck on BTCGuild - Average luck this difficulty is 75.73%. So block generation has slowed.

[bitpop]

Can't wait for update to rejoin with baj

[maqifrnswa]

wow, the hashrate now is over 900Gh/s!

witout increase of DOA....

Whre comes it from 

BFL SCs?

@Kano: Did you ever retry p2pool after flashing your jally to firmware 1.2.5? There may be something in there that is enabling the reports that recently shipped BFL devices work on p2pool. Mine shipped, so next week I can try to do some real tests - play with different firmware revisions to try to confirm the problem and fix.

[yxxyun]

1NastyFRkeUTmMdbMmzggDVTQA6r3ibUoX  this guy has over 200Gh/s on p2pool

[xgtele]

1NastyFRkeUTmMdbMmzggDVTQA6r3ibUoX  this guy has over 200Gh/s on p2pool

Yeah, nasty things are coming 

[maqifrnswa]

1NastyFRkeUTmMdbMmzggDVTQA6r3ibUoX  this guy has over 200Gh/s on p2pool

Yeah, nasty things are coming 

yeah, nasty 
https://bitcointalk.org/index.php?topic=86854.0

5x BFL 60GH/s ASIC Miner
5x BFL BitForce Single FPGA
1x ASICminer USB Block Erupter

[baloo_kiev]

Brief report of p2pool + AM block eruptor blade investigation

1) Blade always works on difficulty 1, regardless of what server tells, so p2pool must always provide diff 1 pseudoshares to account solved work properly. This does not affect real shares difficulty, which can be tuned as usually.

2) Blade does not use long polling. Instead, it makes about 4 getwork requests per second. Looks like it makes as much requests as it can, each providing work to one chip. With 32 chips, it means about 8 seconds per full round. Maybe it doesn't send solutions before doing this full round; this must rersult in about 50% DOA. Or maybe results are put into queue and wait while software is busy requesting new work. In both cases, running it locally may help. Also, I'm not sure that real share DOA will be as high as pseudoshare DOA.

3) "p2pool + stratum proxy + AM blade" setup has some authorization-related issue. This is all I can tell by now, will try to get more details.

P.S. With the difficulty tweak, it works giving about 50% pseudoshare DOA. Real share efficiency is unknown because of little statistics. Those who have AM blades may give it a try at 78.27.191.182:8353 (with your payout address as username).

P.P.S. A question to any developers here. May I officially state that AM blade software is a piece of crap? No stratum, no long polling and constant difficulty in the year 2013. It might be OK for their internal mining but not for a sold product!

[lenny_]

Thank you very much forrestv and baloo_kiev for your efforts and development. I hope that these Blades will be finally working fine with p2pool soon.