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

I don't think it's #2.  I have it running through a proxy pointed to Eligius, and Eligius restarts every 30 seconds or so as well, yet I don't have the problem.

M

Yet it works fine with a conventional pool, like Eligius?  That would also mean everyone else with S2s would have the same problem?

M

Its the host controlling your S2 man , probably terribly underpowered.

He's talking about the time between shares, but it's actually 30 seconds now.

Hi phillipsjk,

I'm aware of the block size change in the 0.9.* clients; however, I'm not sure that would explain the latency spikes that are currently happening.  I've had 0.9.1 installed and running since release and it is only within the past few days that the latency has gone haywire.  My normal latency is ~0.4s, which by itself isn't that good since guys running the entire thing in a RAM drive get ~.02s.  In the past 2 days, the latency has spent many hours of ~1s latency.  It isn't only my node, either.  Nothing has changed on my end in terms of hardware/software/load/network traffic/etc.  Even if something had changed on my end, it wouldn't be reflected across multiple nodes on the network.


Curious... what 10 second restarts?  Anyone with an S2 on p2pool also experiencing this?  How about one of the SP-10 Dawsons?  Dragon 1T?

Bitcoind version 0.9 changed the default blocksize from 500kB to 750kB. That may explain it. You can test by telling Bitcoin to make 500000 byte blocks again:


The blockprioritysize (number of free transactions included) was lowered as well (I set it to ~1/3)

I've come to the conclusion my S2 doesn't work properly with p2pool because:

1 - p2pool can't feed it work fast enough.  Not likely because of vardiff, setting it to the max it seems to support (1024) doesn't change things
2 - the 10 second restarts
3 - something with my hardware

I'm thinking it's #2.

M

Hi!

I was minig at an public p2pool nod for a while and get paybents for every bloch founf - however, for yesterday's two I got no paymernt - how can I found out what went wrong (I still have my address at the activ users and predicted payment list.

Thanks for answer in advance!
MJ

Just got my node up and going at http://96.38.175.165:9332 it's setup as a public pool should be able to handle a few users, hosted out of Reno nv

I only have one S2 at the moment.  I saw a spike in the latency as well on my p2pool node.  This low hashrate on p2pool isn't a recent phenomena, I've been playing with it for about 5 days now trying different things.  Only recently did it occur to me it's limited to p2pool only.

M

I saw your other post as well.  I missed the part where you stated this was solely a p2pool issue, and that Eligius reports at 990GH/s.  I checked the graphs on your node, and the attached miners seem to have the proper mean hashing speed (assuming of course your S2s are on your node) .

What really strikes me as odd is the S2 itself reporting the lower-than-expected hash rate exclusively when you point it to p2pool.  I wonder if the version of cgminer the S2 ships with might be the culprit?  I know kano had released a new binary of cgminer for the S1.  Maybe he's got one for the S2 as well?

Wish I could be of more help.  In your other thread you mentioned there is one chain not reporting temps, but only a single X in the list, so I'm not sure that would be the problem.  Again, I keep falling back to your statement that it works properly on Eligius, but not on p2pool.  That really seems to rule out a hardware problem.  Since you've already changed out the PSU with no effect and made sure the boards are properly seated, I'm out of other ideas.

EDIT: p2pool itself has been acting up recently.  For example, there are a number of threads wondering why the getBlockTemplate latency is spiking across the board.  I'm a victim of it as well.  It's upwards of 1s now.  Between 3am and 8am this morning the latency was normal, but before and after it sits at least 2.5 times higher than normal.  I saw the same trend on the graphs on your node.  Another thing I've noticed is that my local DOA percentage has climbed.  Initially I was running about 1% or so... now I'm averaging about 4-6%.  You can see the steady progression upwards on the monthly graphs on my node.

Can you give me the link you are referring to?  As I said it only happens with p2pool.  And I replaced the PSU.

M

mdude77, there's some discussion in the S2 hardware thread about the lower-than-expected hash rates.  People are blaming a few things:

• Under-powered PSU with which S2 ships
• Crap soldering of chips to the boards

I've been debating between the S2 and the SP-10 Dawson as my next hardware purchase.  The price difference is pretty significant - at this point with S2 coupons (or 112bit's group buy) I could almost get 2 of them for the price of a single Dawson - even if I were to jump on RoadStress' group buy of the Dawson.  Unfortunately I don't know if I've got enough available circuits in my house to handle 2 more miners - and paying someone outlandish rates to host in a data center isn't going to happen, either.  I might be calling in the electrician to see if I can get a new 240/30 circuit and install my own rack/cabinet at home.

Anyhow... that was way off topic, sorry about that

I thought of that.  The problem is the S2 is also reporting the same hashrate.

M

Dead shares. My 36gh/s has between 2 and 3gh/s dead shares so effective hash rate as calculated by p2poo is lower than actual??

Anyone else here using an S2 with p2pool?  I noticed something peculiar.  When I have it pointed to p2pool, my S2 (and p2pool) reports it around 924gh/s, when it should be 1th/s.  I've tried it on several different nodes with different difficulties, with the same result.  That's after letting it run for a day or so.

I can't tell if I'm getting the proper shares or not because the pool hashrate keeps jumping all over the place. I think I'm a little low, but not 100% sure.

Yet if I point it at Eligius, it's about 990gh/s, give or take.

M

Latency is much better now.

Never mind   
Total: 1 (Orphan: 0, Dead: 0)

Ok.. i over reacted. Sorry about that.

The latency seems pretty high, but I don't know if that is related. It's been .2-.3 for last few days and now .8 for last few hours. I thought I would have seen one share by now after my restart. Just paranoid..lol. I added new miner last night and just want to make sure everything is good.
I think node is fine and I would have better luck relaxing especially after seeing 1.

Node uptime:   4h 24m 13 s
Expected time to share:   2h 31m 23 s
Shares:   Total: 0 (Orphan: 0, Dead: 0

take care

You'll see stale blocks more than on normal pools with p2pool, it's pretty normal as far as I know.

I've only got 2 shares in the last 48 hours but then i'm only hashing at 36gh/s

have not caught a share in 4 hrs.. starting to wonder if something is wrong after restart ha.

Should I be worried about these? I didn't see any before I restarted today. I searched around and it doesn't seem like an issue on my node or miners from what I can find.
Any info guys? I'm still reading and searching.

Punishing share for 'Block-stale detected!