Quote from: sammy007 on May 09, 2014, 10:52:46 AM

Quote from: skabbo on May 09, 2014, 10:48:37 AM

Quote from: Doom4535 on May 08, 2014, 02:33:07 PM

Quote from: skabbo on May 08, 2014, 01:30:37 PM

Is anyone else getting speed greatly under-reported at HashInvest? I have 2x 290x and 1x 750ti pointed at it, for a total of about 1mh, and the page is reporting about 100kh (<1% rejects on my end and good WU).

http://188.226.224.163/?vtc=VqMf5TdEYi8AG5so6qwZarJ1DkecoJmCEo&mon=PJSabots1KyFy2NtzL3t6KTEQSGQRnHafi
Using Vertminer on BAMT 1.6 (for the two 290x)

Any suggestions? Thanks much

Edit: a half hour later and it's reporting about 68kh. Sad

What are your scan time, queue, and expiry settings? I've had simular problems on p2pool nodes if I didn't use a queue setting of 0

Queue was 0, but scan-time and expiry were both too high. Lowering them [very briefly] bumped the reported hashrate up to 900kh, but since then it's settled back down to around 300kh. Payouts seem much more regular now (I'm on plx.qemulab now - was getting the under-reported hashrate on both p2pools though).

This is my pool, I have no idea why you got low hashrate, I already said that I pointed one of my rigs to pool and noticed average hashrate.
You can try to tune your rig on regular p2pool if you think something wrong with my pool. And also, you can install your own p2pool node.

Nah, I don't think it's anything to do with your pool - I've always noticed low reported hashrates on p2pools, even after lowering queue to 0, and scan time & expiry below 5 (1, in this case). Occasionally the reported speed will bump up (right now it says 602 - at one point it said 900) so I'm not too worried. Before I changed the scan time and expiry when the reported hashrate never went above 1/10 of what it should be (and payouts were equally low), then I was concerned. Now it seems to just be fluctuating normally.