xmr-node-proxy icon indicating copy to clipboard operation
xmr-node-proxy copied to clipboard

low hashrate on pools compared to hasrate on proxy

Open Makanar opened this issue 7 years ago • 9 comments
trafficstars

on the proxy, it shows I have 64 miners connected at ~2000 h/s, avg difficulty of 217. However, on supportxmr.com, it shows I am only getting 1.3 h/s (EDIT 1300h/s) from the proxy. This is after all night even, Mining directly to the pool shows the correct value, so it is an issue either with the proxy or my settings. Please help.

{ "pools": [ { "hostname": "pool.supportxmr.com", "port": 7777, "ssl": false, "allowSelfSignedSSL": false, "share": 0, "username": "4.....", "password": "steve:[email protected]", "keepAlive": true, "coin": "xmr", "default": true } ], "listeningPorts": [ { "port": 7733, "ssl": false, "diff": 5000, "coin": "xmr" }, { "port": 3333, "ssl": false, "diff": 1000, "coin": "xmr" } ], "bindAddress": "0.0.0.0", "developerShare": 0, "daemonAddress": "127.0.0.1:18081", "coinSettings": { "xmr":{ "minDiff": 100, "maxDiff": 300000, "shareTargetTime": 6 }, "aeon":{ "minDiff": 100, "maxDiff": 300000, "shareTargetTime": 15 } } }

Makanar avatar Dec 23 '17 19:12 Makanar

Same here. I'm showing 2000 h/s on the proxy and only 980 from supportxmr. Something is off here...

runningwithbeer avatar Dec 23 '17 21:12 runningwithbeer

@Makanar : your share value is incorrect. You should put “share” : 100 . It means 100% hash rate going go supportxmr

bobbieltd avatar Dec 26 '17 14:12 bobbieltd

#82 Developer share and share in the pool are diffrent things.

bobbieltd avatar Dec 26 '17 14:12 bobbieltd

Then if 0 mean 0%, then I should be getting nothing. I think because it is the only pool and set to default share does not matter. Either way, I assume this has nothing to do with my problem of only getting roughly 2/3 of the hashrate I should be getting.

Makanar avatar Dec 26 '17 21:12 Makanar

@Makanar Quote : “However, on supportxmr.com, it shows I am only getting 1.3 h/s from the proxy.” . It’s not 2/3 hashrate and nearly 0 h/s. That’s reason why I thought because share value was 0. With 2000 h/s, you can try port 5555 on supportxmr. Anyway, I often enccounter lower hash rate on supportxmr comparing with the proxy but it’s not much.

bobbieltd avatar Dec 27 '17 07:12 bobbieltd

Set your share target time to 1, you likely have an extremely low number of miners, so you're not submitting shares fast enough.

Snipa22 avatar Dec 27 '17 07:12 Snipa22

do we have to restart proxy server after we made changes on config file?

turtlepile avatar Jan 01 '18 18:01 turtlepile

@Snipa22 I have 60+ miners as stated in description. Is that considered a low amount of miners in which I would need to lower the target share time from 15? It is already at 6.

@bobbieltd Sorry, that was supposed to be 1.3 KHS, 1300 h/s.

Makanar avatar Jan 03 '18 06:01 Makanar

@Makanar Your hashrate at 1.3 kh/s is 21 h/s. Low-side diff at 15 second STT should be 300 diff. You need to play with the settings.

Snipa22 avatar Jan 06 '18 18:01 Snipa22