Lower hashrate through proxy

[billyfordon]

I just tested this proxy with nicehash to see if it could withstand high load. Long story short: nicehash reports at least a 25% decrease in hashrate. It does not seem to come from rejected shares, but rather the proxy itself is not handling the load or doing something stupid and not forwarding all shares to the pool. Any ideas what is causing this?

Machine running the proxy is powerful enough, it is in Europe and has at most 20ms latency to nicehash. Different pools tested, with low latency as well.

[BScrk]

Hi
If I understand you are sending nicehash hashrate on zecproxy and then the zecproxy hashrate on a pool (like this : Nicehash ---> zecproxy ---> pool) ?
If yes, the hashrate decrease is normal : zecproxy is designed to aggregate local network/subnets hashrate on an unique internet access-point. You are sending hashrate from nicehash to your box/computer and then sending back the hashrate from your box/computer to the pool you will lose time / bandwidth / hashrate for nothing (Nicehash already having it own hashrate aggregator).

[appkoders]

So this is for local network use only? what causes the 25% decrease in hashrate is it all caused by latency?