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

I am sorry but I am finding myself repeating these details over and over, here...
I have nearly no problems on any other pool. These problems only happen on p2pool, whether my own node or not. It's winter in southern hemisphere + my s5 is new + new model with heat sink + air conditioned room.
One board stops hashing, then returns after a few minutes, once every 2-3 days for a few minutes on other pools. This happens ~every 2 hours on p2pool. Not only that, but hashrate is slightly lower, even with igor white's firmware or kano's fix. Without them it is much lower.

And yes, I run 425mhz on other pools just fine. 0.044% hw. It was 0.02% a few weeks ago though  
I did a lot of testing and found 425mhz to be the best spot for me. It varies from person to person, miner to miner.

I will be keeping an eye on p2pool and this thread and eventually will be testing out stuff. For now, I will have to go to eligius and trust/hope they will not do anything wrong.

Yep, 425 is quite overclocked.  I had a farm of over 40 units and only 4 of them reliably worked at 425.  Most of them were capable of hitting 412.5, but not sustaining it.  387.5 was where the majority of them were happy and honestly the difference between 387.5 and 425 is not that much.

I'm not real surprised it's not stable at that rate. 

Agreed. Not all S5's are OC'able to the same extent, some don't like it at all. 425 is very OC'd - I would restart it at standard settings & slowly work your way up until you notice a failure, then back it up a notch. You'll find it will be not only more efficient, but less hassle also.

looks more like miner fail than a pool failure in your case.

just me though, i'm ok with a little lower reported hashrate. end of the day, the payout counts the most.

I am not lazy or dumb, and I doubt people who tried to mine on p2pool and failed mostly are. Dogie is bitmain's shill and variance isn't to blame. My s5 isn't perfect and already fails sometimes on eligius (and ghash as secondary), but fails much more often on p2pool and I also get a lower hashrate, despite trying igor-white's firmware and kano's fix. That happens on my node or anyone else's!

Here, gave it another try just now: http://prntscr.com/7hqw1c s5 425mhz
All in all I am lucky if I get 1300gh/s long run hashrate on p2pool while I get no less than 1360gh/s on others. I find it sad mining is so centralized but I have no other option, at least I am not going for these big pools such as antpool, discus etc...

The fact that you even know what Linux is, and have successfully gotten p2pool and merge mining up and running puts you far ahead of a typical user.  I happen to agree with you in that getting a node up and running is a pretty trivial task with a bit of research and reading; however, people expect a simple plug-and-play operation and running your own node is not.

As for dogie's comments in other threads, they can be addressed in the appropriate threads.  I was simply responding to his reply here, and his statements aren't off the mark.

yes, since 0.9.1 (of bitcoin core) ... they don't support WinXP (32).
  but i don't only have bitccoin core on this "machine" ... and all others softwares work flawless (1 reboot after 45 days usually).

v0.9.1 work flawless with P2Pool node and miner software.
since this, all version crash with RPC server activate.

don't crash in Bitcoin Core node or wallet.

and, to be more specific ... it's not the P2Pool or Miner software that it has a problem : it's Bitcoin Core that it crash ! (P2Pool don't crash, Miner Software don't crash).

---

Well, it's not a problem for the planned task manager ...   kill and launch is the solution now.

---

I have solomining on 2014 ... then P2Pool since 2015 and only have this problem since i (must) left the 0.9.1 because of version 3 of block creation.

I'm no Linux freak, yet I had no problem setting up my own node with merge mining, it's not hard at all. All that is required is plenty of reading & some common sense. If a noob user like me can do it - anyone can. Let's not make it sound harder than it really is.

As for the bitmain "support" troll, his post history on p2pool (the bitmain bodged version) tells it's own story.

No, it really isn't.

Inconsistent earnings are going to happen on virtually very pool with a low percentage of the network's hash rate.  P2Pool is no exception here.  It's called variance.

High pings.  This is only the case if you're mining on somebody else's node.  Most new users who don't have as much technical experience aren't going to bother setting up their own node (sadly) and will instead mine on other people's nodes.  This leads to the next point...

Higher complexity - setting up and running your own p2pool node requires a bit of technical know-how.  Ideally you've got a dedicated *nix server sitting somewhere, have installed the proper dependencies and have tuned things.  You also need to be running a full Bitcoin node.  Now, if you're mining on somebody else's node, it's just as simple as mining on any pool like kano.is.  However, you're at the mercy of that node operator and whether or not he's competent.

Lower performance / earnings.  Specific hardware will indeed have lower performance or not work at all on p2pool.  This is well known.  Earnings were addressed in the first point.

Now, if you don't feel like running your own node, there are plenty of operators that have proven themselves to run a tight ship.  In these cases, mining on p2pool is just as easy as any other pool.  If you've got the technical wherewithal or just feel like a bit of learning, running your own p2pool node is very rewarding.

What complete & utter rubbish!

EDIT: I see now......



bitmain "support" guy

Please don't post about subjects you know nothing about.

The typical reasons are inconsistent earnings due to low network %, high pings, higher complexity, lower performance / earnings. P2Pool is a hard sell towards new users.

Don't know about others but I run into same problems running my own node or mining on other people's p2p nodes.

There is something wrong with your setup.  I've been successfully running my own node for well over a year and have never experienced this type of behavior.  I have had the 0.10.x core since release candidate running without issue.

I saw somewhere (didnt find the thread) that S5 have problem with P2Pool but that S3 and S4 have no problem.
Maybe its a firmware problem.  

Why do conman doest work on P2Pool?

i have no crash last 5 days at least using bitcoin core qt v0.10.2 running on widows via python

i am sure there's something wrong with the crash setup.

you can visit my node to have a look.

P2pool works fine with Bitcoind/qt. Can you provide more info?

ie: What OS/distro?

Do you have all the required dependences?

Have you built from source or using pre-compiled binaries?

What hardware are you using?

etc......

Tak.

me too ... but if no person can maintenance the P2Pool when Bitcoin Core upgrade ... Bitcoin Core v0.9.5 and early crash with a P2Pool.

I need to kill and relaunch P2Pool node + Bitcon Core + Miner every hour for ... hash.



Bitcoin Core work flawless with SOLO MINING (No P2Pool but with miner software).
Bitcoin Core close when P2Pool node is already working ... thaht why i must kill P2Pool before i relaunch Bitcoin Core v0.10.x

---

I have try to mine on remote P2Pool ... but it don't decrease difficulty (like it stay at 500 when i must have a 12-8 on my little miner).

Did they now? Can you yell me who told you this at bitmain? I'm afraid bitmain & their "support" staff are pretty clueless when it comes to p2pool, as their attempted clone of it clearly shows. I wouldn't take any notice of him/them.

Getting a slightly lower hash rate is normal with p2pool, it's always been like this I believe. If your units are locking up, try lowering the OC settings - you're probably working them too hard.

When only 3 of my 4 S5 chains were working, I was mining on P2Pool with very low variance in the hashrate. Now that I have all 4 chains running, I get high hashrate variability, and sometimes a miner just stops hashing as chalkboard17 says here. Bitcoind GetBlockTemplate Latency seems to be the bottleneck. I currently have a mean latency of 1.37 sec., but sometimes the latency is at most 3 sec.! My hashrate on both S5s is about 0.1 Th/s slower than optimal (1.1 Th/s).

I'm using cgminer 4.9.0 (http://ck.kolivas.org/apps/cgminer/antminer/s5/4.9.0-150105/cgminer) with "--queue 0". Perhaps "-queue" should be a tad > 0? Would that help with the GetBlockTemplate Latency issues?

Update: I just tried "--queue 1" (which is cgminer's default; the default on S5s is something over 8000, which is WAAY too big to be useful with P2Pool), and it does not seem to be helping.

Trust me, other people and I who faced issues tried that. I get slightly lower hashrate on p2pool and also one hashing board stops once in awhile, decreasing further hashrate. Have a look at my previous posts.