Proxy settings - poor performance

[ruzickap]

Hello.

I tried the xmr-node-proxy but I'm not able to set it up correctly. When I'm using the proxy I'm getting very poor performance comparing to "direct pool" access.

I installed the xmr-node-proxy with the following config.json:

{
  "pools": [
    {
      "hostname": "mine.xmrpool.net",
      "port": 80,
      "ssl": false,
      "username": "wallet_address",
      "password": "proxy",
      "keepAlive": true,
      "coin": "xmr",
      "default": true
    }
  ],
  "listeningPorts": [
    {
      "port": 88443,
      "ssl": true,
      "diff": 1500,
      "coin": "xmr"
    }
  ],
  "bindAddress": "0.0.0.0",
  "developerShare": 0,
  "coinSettings": {
    "xmr":{
      "minDiff": 100,
      "maxDiff": 300000,
      "shareTargetTime": 15
    }
  }
}

I connected one miner (for testing purposes) which is using "xmr-stak-cpu" and has about 50 H/s. Here is the output from the miner once it's connected to proxy:

[2017-07-27 11:21:55] : Connecting to pool XX.XX.XX.XX:88443 ...
[2017-07-27 11:21:55] : Server fingerprint: SHA256:RAC/du...38=
[2017-07-27 11:21:55] : Connected. Logging in...
[2017-07-27 11:21:56] : Difficulty changed. Now: 1500.
[2017-07-27 11:22:36] : Difficulty changed. Now: 555.
[2017-07-27 11:24:06] : Difficulty changed. Now: 810.
[2017-07-27 11:25:36] : Difficulty changed. Now: 750.
[2017-07-27 11:26:21] : Difficulty changed. Now: 660.
[2017-07-27 11:27:06] : Difficulty changed. Now: 720.
[2017-07-27 11:27:51] : Difficulty changed. Now: 840.
[2017-07-27 11:28:36] : Difficulty changed. Now: 975.
[2017-07-27 11:29:21] : Difficulty changed. Now: 900.
[2017-07-27 11:30:06] : Difficulty changed. Now: 855.
[2017-07-27 11:30:51] : Difficulty changed. Now: 780.
[2017-07-27 11:31:36] : Difficulty changed. Now: 735.
[2017-07-27 11:32:21] : Difficulty changed. Now: 705.
[2017-07-27 11:33:06] : Difficulty changed. Now: 720.
[2017-07-27 11:35:21] : Difficulty changed. Now: 705.
[2017-07-27 11:36:06] : Difficulty changed. Now: 720.
[2017-07-27 11:36:51] : Difficulty changed. Now: 705.
[2017-07-27 11:37:36] : Difficulty changed. Now: 690.
[2017-07-27 11:38:21] : Difficulty changed. Now: 675.
[2017-07-27 11:39:06] : Difficulty changed. Now: 660.
[2017-07-27 11:41:21] : Difficulty changed. Now: 675.
[2017-07-27 11:42:06] : Difficulty changed. Now: 660.

I checked the hash rate on the pool and it's around 5 H/s. When I use the connection directly to the pool I got about 45 H/s see the output:

[2017-07-27 12:39:30] : Connecting to pool mine.xmrpool.net:80 ...
[2017-07-27 12:39:30] : hwloc: memory pinned
[2017-07-27 12:39:30] : hwloc: memory pinned
[2017-07-27 12:39:30] : hwloc: memory pinned
[2017-07-27 12:39:30] : hwloc: memory pinned
[2017-07-27 12:39:30] : Connected. Logging in...
[2017-07-27 12:39:30] : Difficulty changed. Now: 7000.
[2017-07-27 12:39:38] : Difficulty changed. Now: 11053.
[2017-07-27 12:40:38] : Difficulty changed. Now: 4920.
[2017-07-27 12:41:38] : Difficulty changed. Now: 2610.
[2017-07-27 12:42:38] : Difficulty changed. Now: 1770.
[2017-07-27 12:43:38] : Difficulty changed. Now: 1530.
[2017-07-27 12:44:38] : Difficulty changed. Now: 1230.
[2017-07-27 12:45:38] : Difficulty changed. Now: 1020.
[2017-07-27 12:47:38] : Difficulty changed. Now: 1200.
[2017-07-27 12:49:38] : Difficulty changed. Now: 1320.
[2017-07-27 12:50:38] : Difficulty changed. Now: 1260.
[2017-07-27 12:51:38] : Difficulty changed. Now: 1170.
[2017-07-27 12:53:38] : Difficulty changed. Now: 1290.
[2017-07-27 12:56:38] : Difficulty changed. Now: 1350.
[2017-07-27 12:57:38] : Difficulty changed. Now: 1290.
[2017-07-27 12:58:38] : Difficulty changed. Now: 1200.
[2017-07-27 13:00:38] : Difficulty changed. Now: 1230.
[2017-07-27 13:01:38] : Difficulty changed. Now: 1260.
[2017-07-27 13:03:38] : Difficulty changed. Now: 1230.
[2017-07-27 13:05:38] : Difficulty changed. Now: 1260.
[2017-07-27 13:06:38] : Difficulty changed. Now: 1290.
[2017-07-27 13:07:38] : Difficulty changed. Now: 1230.
[2017-07-27 13:08:38] : Difficulty changed. Now: 1200.
[2017-07-27 13:11:38] : Difficulty changed. Now: 1170.
[2017-07-27 13:12:38] : Difficulty changed. Now: 1140.
[2017-07-27 13:14:38] : Difficulty changed. Now: 1170.
[2017-07-27 13:15:38] : Difficulty changed. Now: 1140.
[2017-07-27 13:16:38] : Difficulty changed. Now: 1170.
[2017-07-27 13:18:38] : Difficulty changed. Now: 1140.

This graph is showing miner using proxy and than without proxy:

Any idea what can be wrong? (probably in the proxy setting)?

Thank you...

[longailend]

Hello. At first thank to all devs for this product. But I`m having same issue, any suggestions?

[sneaker8650]

as far as i´m informed, you should at least have 10 miners, while using the proxy. You will only gain a performance improvement, if you have many miners, which are connected to the proxy. If you can, add some more nodes. I am running the proxy with ~33 miners, performance is great, so i cant complain.

[Snipa22]

The proxy is not designed for particularly low connection counts. Due to the design of the proxy, which is designed to concentrate high-ish number of miners, it has special exceptions for level of work from the main servers. Due to this, single/low miner counts do not tend to serve the proxy well.

Functionally, until you get past 10-15 miners, you're likely to see an even-response, or worse performance.

[ruzickap]

Hello.

I tried to connect 10 miners with 46 H/s each in average to the proxy. In the pool I can see 450 H/s, but when I point all the miners to the proxy I got about 70 H/s.

Proxy is showing 440 h/s, but it's still 10 h/s less when comparing it with "no-proxy" usage:

1|proxy    | 2017-07-28 13:44 +00:00: The proxy currently has 10 miners connected at 440 h/s with an average diff of 658
1|proxy    | 2017-07-28 13:44 +00:00: Received new block template from mine.xmrpool.net
1|proxy    | 2017-07-28 13:44 +00:00: The proxy currently has 10 miners connected at 440 h/s with an average diff of 658
1|proxy    | 2017-07-28 13:44 +00:00: The proxy currently has 10 miners connected at 441 h/s with an average diff of 663
1|proxy    | 2017-07-28 13:45 +00:00: The proxy currently has 10 miners connected at 441 h/s with an average diff of 663
1|proxy    | 2017-07-28 13:45 +00:00: The proxy currently has 10 miners connected at 438 h/s with an average diff of 663
1|proxy    | 2017-07-28 13:45 +00:00: Received new block template from mine.xmrpool.net
1|proxy    | 2017-07-28 13:45 +00:00: The proxy currently has 10 miners connected at 438 h/s with an average diff of 657
1|proxy    | 2017-07-28 13:45 +00:00: The proxy currently has 10 miners connected at 439 h/s with an average diff of 657
1|proxy    | 2017-07-28 13:46 +00:00: The proxy currently has 10 miners connected at 441 h/s with an average diff of 657
1|proxy    | 2017-07-28 13:46 +00:00: Received new block template from mine.xmrpool.net
1|proxy    | 2017-07-28 13:46 +00:00: The proxy currently has 10 miners connected at 439 h/s with an average diff of 661
1|proxy    | 2017-07-28 13:46 +00:00: Received new block template from mine.xmrpool.net
1|proxy    | 2017-07-28 13:46 +00:00: The proxy currently has 10 miners connected at 441 h/s with an average diff of 661
1|proxy    | 2017-07-28 13:46 +00:00: The proxy currently has 10 miners connected at 440 h/s with an average diff of 661
1|proxy    | 2017-07-28 13:47 +00:00: The proxy currently has 10 miners connected at 440 h/s with an average diff of 661
1|proxy    | 2017-07-28 13:47 +00:00: The proxy currently has 10 miners connected at 439 h/s with an average diff of 661
1|proxy    | 2017-07-28 13:47 +00:00: Received new block template from mine.xmrpool.net

I have no idea why pool xmrpool.net is showing only 70 h/s, but that's count.

Here is the graph:

Anyway even if I connect 1 miner to the proxy (50 h/s) I expect that 50 h/s will be send to the pool - and pool will recognize it.

-> That's the way how "any" proxy should work...

You should always get at least the same traffic (or better) which is being send to proxy (no matter how many clients are connected).

[Snipa22]

So, there's 2 core issues with how you're looking at this.

1. You're likely connecting the proxy to a very high difficulty port.
2. You're likely configured to have your miners at high difficulty.

45 h/s is trivial for the proxy to handle. In order to properly gauge your level of work, make sure you're connecting to a low enough difficulty port on the pool, as well, set your proxy port to h/s * coinSettings//shareTargetTime If you're auctually doing 45 h/s, with the default configuration, your port diff should be ~1k. Based on the default configurations (5k/10k), you wouldn't submit enough shares to the proxy to be accepted. If you have a high diff at the pool side, it's even worse, as those shares have to get over that hump.

As for your comment:

Anyway even if I connect 1 miner to the proxy (50 h/s) I expect that 50 h/s will be send to the pool - and pool will recognize it.

-> That's the way how "any" proxy should work...

You should always get at least the same traffic (or better) which is being send to proxy (no matter how many clients are connected).

This is patiently incorrect, as you don't seem to understand how stratum proxies work. Stratum proxies exist for ease of miner management, and for handling high connection counts without requiring the extremely high amount of share validations required by a pool taking connections. Functionally, the pool attempts to get 10 shares/minute from your proxy. This is equal to 5 miners (Based on standard diff timings of 30 seconds/etc.). The pool will adjust the difficulty values being sent to your proxy to handle this. If the initial difficulties are too high, your proxy will take an excessive amount of time to self-correct.

My personally hosted proxies with 650+ connections are running at equivalent traffic and/or h/s, but have received the proper levels of tweaking to ensure that they work properly. You can't blindly deploy the proxy and expect it to work, knowledge of how difficulty is calculated and things of that nature are needed until full documentation is written.

Quick edit - Just re-read your first post. 1500 is too high, assuming you're using 45 h/s and the default settings. Use 750. As for the pool port, XMRPool.net defaults to 7k on 80. With 10 miners at 45h/s ea, you should see 450 h/s. Verify you're seeing this in the proxy logs:

0|proxy | The proxy currently has 551 miners connected at 16785 h/s with an average diff of 916

Based on standard configuration: https://github.com/Snipa22/nodejs-pool/blob/master/lib/pool.js#L399

You should aim for 6 second share times for your to-pool diff. This would be a semi-idealized value at 2.7k diff, assuming you're seeing 450 h/s at the proxy.

[slayerulan]

I have same problem too. With 600+ connections i got only 3.3kh/s.

1|proxy | 2017-08-01 11:25 +00:00: The proxy currently has 626 miners connected at 3267 h/s with an average diff of 46

@Snipa22 can you post your current tweaked config?

Thanks

[Snipa22]

Sorry guys, been super busy.

https://tb.snipanet.com/rtfe/

{
  "pools": [
    {
      "hostname": "mine.xmrpool.net",
      "port": 7778,
      "ssl": false,
      "share": 20,
      "username": "46XWBqE1iwsVxSDP1qDrxhE1XvsZV6eALG5LwnoMdjbT4GPdy2bZTb99kagzxp2MMjUamTYZ4WgvZdFadvMimTjvR6Gv8hL",
      "password": "proxy",
      "keepAlive": true,
      "coin": "xmr",
      "default": true
    }
  ],
  "listeningPorts": [
    {
      "port": 3333,
      "ssl": false,
      "diff": 1000,
      "coin": "xmr"
    }
  ],
  "bindAddress": "0.0.0.0",
  "developerShare": 1,
  "daemonAddress": "127.0.0.1:18081",
  "coinSettings": {
    "xmr":{
      "minDiff": 100,
      "maxDiff": 300000,
      "shareTargetTime": 30
    }
  }
}

Is my current config.

[dorimanx]

Hey, thanks for this aswesome proxy! After some tuning i see great performance!

DORI-FARM > 11-08-2017 15:32 +00:00: The proxy currently has 10 miners connected at 4092 h/s with an average diff of 6022 MEGA-SWARM > 11-08-2017 15:32 +00:00: The proxy currently has 40 miners connected at 3196 h/s with an average diff of 1218

50 miners drill :) supportxmr.com

running 2 proxy pids on one server, each listen on different ports!

Great work! respect to you @Snipa22 :+1:

[tosokr]

Hey dorimanx, what was your tuning? Please share

[dorimanx]

@tosokr

Here you go. https://pastebin.com/cbmwkhYC

2 farms! with vardiff changes and port splits to prevent collisions!

[Alex378563872624837]

Hi, regarding performance, where is the log file located? And is it possible to see how much work a individual worker did, or which worker is connected?

[pslobo]

@Snipa22 I'm hoping you can help me with fine tuning something. I currently have 10 miners each with about 6-700H/s. What is the best diff to place in listening_ports to optimize the proxy and miners?

[BamaStangGuy]

I have miners that range from 45 /hs CPUs to 1250 h/s GPU rigs. Is it smart to pour them all into one proxy mining on pool.supportxmr.com:7777? What would I choose the difficulty at in the proxy config? What about share time?

[tzhbami7]

share time is a little bit confusing for me as well :/ do I need to set it to the avg time of all connected miners or can i leave it at 15 seconds - avg time for me is 25 seconds.

[tzhbami7]

Mhh.. maybe I found something regarding the sharetime. https://arstechnica.com/civis/viewtopic.php?f=18&t=1396927

Search for sharetime

[bartonaz]

@Snipa22 Thank you very much for this great tool. I have 8 miners that I connect to a single pool through this proxy server, and I've noticed in the pm2 monit display that at the beginning the total hashrate is high for the first ~10 seconds, but then it drops by ~30%, while the difficulty stays almost the same, or sometimes slightly lower. Is it just a side effect of the way the hashrate and average difficulty are calculated by the proxy server, or is the proxy config really non-optimal and some slow miner is stopping other 7 from working at full power? How would you recommend to check this?

[andreytsushima]

Hi i've the same problem, i put 13 miner for test and the monit show me: The proxy currently has 13 miners connected at 921 h/s with an average diff of 1067 and the supportxmr dashboard show me: proxy | 619 H/s | 682 H/s I'm using low end port 3333 to connect my proxy. and set diff to 960. Each minner without proxy have hash 62-90 H/s What's wrong?

[fogoat]

Remember pools do not know our exact hash rate because they have to calculate your client hash rate based on the difficulty when the share was accepted. It is just an estimation. It should be close to your actual hash rate if you give it 30 minutes to create an average.

[razorman8669]

2 questions: 1) The difficulty settings for the port don't really matter that much since vardiff is going to end up adjusting it based on mining performance, right? 2) @dorimanx and @Snipa22 , how come you have share: 80 and share: 20 in your configs [respectively]? wouldn't you want that at 100 if you're only mining to 1 pool? that's supposed to be used to split mining efforts across multiple pools, correct?

[Snipa22]

1. Correct, VarDiff automatically adjusts the diff based on your miner, but the closer it is, the better for performance off the bat.
2. The default config shows off the various features, including showing off splitting hash between pools. :)

[gitbit00]

@Snipa22 can you post the math equations we need to calculate our difficulty and share time variables?

I have 500 miners that each normally hash at 140 h/s @ 3000 difficulty. (1 miner connected directly to mine.xmrpool.net)

When I connect through the proxy, my average hash rate goes down to 60 h/s @ 800 difficulty. My settings are below and I'm connecting them to port 3333.

I tried 15 and 30 for the 'sharetime' variable without much difference.

{ "pools": [ { "hostname": "mine.xmrpool.net", "port": 7777, "ssl": false, "allowSelfSignedSSL": false, "share": 100, "username": "X", "password": "X", "keepAlive": true, "coin": "xmr", "default": false }, { "hostname": "mine.xmrpool.net", "port": 5555, "ssl": false, "allowSelfSignedSSL": false, "share": 0, "username": "X", "password": "X", "keepAlive": true, "coin": "xmr", "default": true } ], "listeningPorts": [ { "port": 8080, "ssl": false, "diff": 750, "coin": "xmr" }, { "port": 8443, "ssl": true, "diff": 10000, "coin": "xmr" }, { "port": 3333, "ssl": false, "diff": 3090, "coin": "xmr" } ], "bindAddress": "0.0.0.0", "developerShare": 1, "daemonAddress": "127.0.0.1:18081", "coinSettings": { "xmr":{ "minDiff": 100, "maxDiff": 300000, "shareTargetTime": 15

[Snipa22]

https://github.com/Snipa22/xmr-node-proxy/wiki/config_review

[prinsbram]

soh i want to know what is better the port : 5555 or the port : 3333 i have around 200 connecting miners but my hash rate is around 100/ 200 H and i have it on the port : 5555 can anybody help me get a higher hash rate if i do something wrong can anybody send me a message thnx

[rwebb0418]

@Snipa22 A little off topic but is it possible to split the share between two different coins within the proxy, while just directing miners to a single listening port?