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

Yeah, I believe it's a system wide problem - might still be worth dropping a post on the NMC thread though - might speed up the fix a bit 

The problem is on the windows side too.  It hung my local p2pool instance.. python would not die.  I had to hard reset the computer.

M

I used to use Atomic Trade - but FSC has gone    (along with my few million.......)

There is a problem with NMC "timeout getting getauxblock" when merge mining - devs are looking into it:

https://bitcointalksearch.org/topic/m.8433539

I turned it off due to high cpu/mem usage until it's fixed.

Peace  

I know that having a low ping helps, but I don't expect every p2pool miner to obey this rule so that's why I wanted to see if it's normal or not but not compared to the global reject. Besides having a 0ms ping is there anything that I can do about this?

Global reject is ~ 15%

This is 13.6% - so i would say it is normal. Variance can give you probably lower but always have a look at global.

Is that a normal orphan rate?

Don't own SP30 but I watch closely the SP thread and I know people with SP30 that mine with P2Pool without issues.

They mine here: http://is.centralcavern.uk:9332/static/

You have an exchange for FSC?

Why do you say until yesterday NMC?

Just so you can compare here is mine... at 4.0TH
I some days get a share an hour and other days 1 share per 6 hours.....

Graphs

Version: unknown 7032706f6f6c2d6e2d6d6173746572

Pool rate: 2.20PH/s (11% DOA+orphan) Share difficulty: 8500000

Node uptime: 11.7 hours Peers: 6 out, 0 in

Local rate: 3.52TH/s (3.3% DOA) Expected time to share: 2.9 hours

Shares: 4 total (0 orphaned, 0 dead) Efficiency: 112.5%

Payout if a block were found NOW: 0.0441345 BTC to xxxxxxxxxxxxxxxxxxxxxxx. Expected after mining for 24 hours: 0.0401 BTC per block.

Current block value: 25.09223858 BTC Expected time to block: 12.9 hours

hope it helps......

(I used to get worried but I just leave it run and some days really make up for the bad ones... after a month of pure p2pool I am ahead of any pool I used to join!)

You are good. DOA looks good compared to public nodes. I bet shares start rolling in. Stay with it   2hrs.. expected. Ha you good. Just restart everything if you are worried.


2.91 TH/s (DOA 70.50 GH/s / 2.43%)
Expected time to share: 3h 40m 1 s

P2Pool BTC

Graphs

Version: 13.4

Pool rate: 2.00PH/s (12% DOA+orphan) Share difficulty: 8820000

Node uptime: 13.5 hours Peers: 6 out, 0 in

Local rate: 5.31TH/s (1.2% DOA) Expected time to share: 2.0 hours

Shares: 1 total (1 orphaned, 0 dead) Efficiency: 0.000%

Payout if a block were found NOW: 0.00823785 BTC to xxxxxxxxxxxxxxxxxxxx. Expected after mining for 24 hours: 0.0665 BTC per block.

Current block value: 25.05109951 BTC Expected time to block: 14.2 hours

 

That's tough to take, but probably bad luck. What are your node stats? I have nothing close to your HR, but I have gone two days @ 1.1 TH/s without a share recently. Bad luck and then from the 16th to 17th did 8-9 days of mining on P2pool. The best day. It made up for it all.
You running on windows on linux?
Got any screen output? Any P2Pool errors?

I have been having some Bitcoind crashing issues lately. I'm trying to work on those now. Pretty sure it's memory related. I hope.

Mining for 13 hours at 5.2TH/s, expected time to share 2.0hrs....

Actual share obtained so far:  1 total (1 ophaned, 0 good) ......


Pure bad luck or setup issue??? 

Seriously, should have got 6 shares under the "expected" scenario.

Ok, so now some questions about peering, in general.

Should you specify your own list of peers?
If so, how many should you consider putting in your config?  Can there ever be too many?
How do you know the performance of your peers, now and historically, to make sure it's good?
Would it help the community to establish a set of well-resourced hosts to act as "root peers", in the same fashion as root nameservers?

So, here's the explanation of my thinking.

If I understand it correctly, the key here is how fast the share information enters the p2p chain, right?  Whomever wins the "share war" gets their place in the chain and their reward, while the ones that get beat out get an orphan.

That being the case, logic should dictate that if your node is well resourced (CPU, RAM, etc), and you have good bandwith, you should be able to get your info to and fro quickly into the overall network, and thusly win that war more consistently.  If you're a small node or not connected well, you'd lose.  That to me seems yet another thing in favor of the larger miners and operations which could be another barrier to adoption and use.

The question then becomes - who are you talking to in the chain, and how fast are they spreading the info to the other nodes for you?

For the larger nodes running open mining for anyone to connect to, this probably isn't a huge concern.  But for those running their own node at home, or us behind firewalls where we can't open up, who you're peering with may indeed have an affect on their stales/DOAs/Orphans, right?

I currently have 6 peers that bitcoind "found" when it started.  I'm behind a firewall and not open inbound.  Doesn't seem to be hurting me having only those 6 peers with none inbound, I have about a 10% share "loss" and my efficiency averages above 100%.  But, is that the case across the board, and if not, can it be made better?

Or, as usual, am I just overly concerned about nothing that really requires that concern?  

Thanks, added SP10, will ask in the spondoolies thread about 30.

I swear there were reports of the KNC Neptune having issues with p2pool as well...

Also, you can add the SP10 as hardware the works properly with p2pool.  I'm not sure of the SP30 because I don't own one

Thanks guys,

I updated the p2pool wiki and added a list of hardware with confirmed issues:

https://en.bitcoin.it/wiki/P2Pool#Interoperability_table

What's profitable today, might not be next week - so I mine them all, just in case......

BTC, DVC, IXC, I0C, GRP, HUC, FSC &, until yesterday NMC - which happens to be the most lucrative atm.......

1.7% is very reasonable, and downright good.  I average between 2-4% DOA on my node.  The global DOA rate is usually in the low-to-mid teens.

Can anyone suggest what is a good additional coin (profitable) to merge with p2pool???
I would assume, that as you are working on BTC you can make additional funds?