Quote from: eduardjs on April 26, 2018, 02:04:39 PM

UPDATE ** Well, stale shares started going from avg 12-13 to 18, even 22. Guess that was it for me.

Hi, I am sorry to hear that.

Can you confirm that your IP is 7x.1xx.2xx.71 and that you don't have multiple IPs so I can better check the logs ?

A quick search in logs gives me the following mining periods (UTC+2 time):

Rig1 online from 16:03:40 to 16:15:23
Rig2 online from 16:03:43 to 16:15:39
then
Rig1 online from 22:05:12 to 23:48:03
Rig2 online from 22:08:42 to 23:50:23

The mining period is really short to see anything, but based on data from ethermine :

- As you said, I see a stale share percentage around 2.0% (1.7%-2.4%) before 16:00 (direct mining)
- 2.0%-3.6% when partially mining with rigproxy (from 16:00 to 16:20)
- 2.9%-4.8% when partially mining with rigproxy (from 22:00 to 23:50)
- 2.0% to 7.4% when direct mining (16:30-21:50 and 00:00-00:30).

Between 17:20 and 22:10 the chart also shows a 30MHs lower than usually reported hashrate.

Quote from: eduardjs on April 26, 2018, 02:04:39 PM

Good luck with the service

Thank you

---
Trying RigProxy over a period of 24hours won't cost anything. If you have a good connection to the pool, you may have no enhancement or low enhancement. In this case, you have no reason to stay if you are only looking for network optimization. The only way to know if you get benefit from RigProxy is to try and see.

If you can deliver shares to ethermine within let say 10ms but rigproxy server is 15ms away, the server can't recover the 5ms.
A pictorial explanation would be : when you need to go 10km away from your home, it is not necessarily faster to take a highway 15km away.

Finally, my advice to all potential users who want to try the service :
Configure rigproxy as poolserver and use direct connection to pool as your first failover (use retrydelay 1 and lower the default 30min of ftime to 5-10), add a second failover if you have none in case the pool goes completely offline.