{"action":"created","issue":{"url":"https://api.github.com/repos/cazala/coin-hive-stratum/issues/37","repository_url":"https://api.github.com/repos/cazala/coin-hive-stratum","labels_url":"https://api.github.com/repos/cazala/coin-hive-stratum/issues/37/labels{/name}","comments_url":"https://api.github.com/repos/cazala/coin-hive-stratum/issues/37/comments","events_url":"https://api.github.com/repos/cazala/coin-hive-stratum/issues/37/events","html_url":"https://github.com/cazala/coin-hive-stratum/issues/37","id":268047921,"number":37,"title":"Implementation of xmr-node-proxy?","user":{"login":"QuantumLeaper","id":6129435,"avatar_url":"https://avatars2.githubusercontent.com/u/6129435?v=4","gravatar_id":"","url":"https://api.github.com/users/QuantumLeaper","html_url":"https://github.com/QuantumLeaper","followers_url":"https://api.github.com/users/QuantumLeaper/followers","following_url":"https://api.github.com/users/QuantumLeaper/following{/other_user}","gists_url":"https://api.github.com/users/QuantumLeaper/gists{/gist_id}","starred_url":"https://api.github.com/users/QuantumLeaper/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/QuantumLeaper/subscriptions","organizations_url":"https://api.github.com/users/QuantumLeaper/orgs","repos_url":"https://api.github.com/users/QuantumLeaper/repos","events_url":"https://api.github.com/users/QuantumLeaper/events{/privacy}","received_events_url":"https://api.github.com/users/QuantumLeaper/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":7,"created_at":"2017-10-24T14:11:22Z","updated_at":"2017-11-03T08:28:44Z","closed_at":null,"author_association":"NONE","body":"Hey, I was wondering if there would be a way to implement this: https://github.com/Snipa22/xmr-node-proxy but with per worker id tracking (total hashes & hashrate). As I understand, it takes multiple workers (example: 4k+) and treats them as one, so there's minimal connections to the pool itself instead of sending all of those connections straight to the pool"},"comment":{"url":"https://api.github.com/repos/cazala/coin-hive-stratum/issues/comments/341644414","html_url":"https://github.com/cazala/coin-hive-stratum/issues/37#issuecomment-341644414","issue_url":"https://api.github.com/repos/cazala/coin-hive-stratum/issues/37","id":341644414,"user":{"login":"Snipa22","id":1285502,"avatar_url":"https://avatars1.githubusercontent.com/u/1285502?v=4","gravatar_id":"","url":"https://api.github.com/users/Snipa22","html_url":"https://github.com/Snipa22","followers_url":"https://api.github.com/users/Snipa22/followers","following_url":"https://api.github.com/users/Snipa22/following{/other_user}","gists_url":"https://api.github.com/users/Snipa22/gists{/gist_id}","starred_url":"https://api.github.com/users/Snipa22/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Snipa22/subscriptions","organizations_url":"https://api.github.com/users/Snipa22/orgs","repos_url":"https://api.github.com/users/Snipa22/repos","events_url":"https://api.github.com/users/Snipa22/events{/privacy}","received_events_url":"https://api.github.com/users/Snipa22/received_events","type":"User","site_admin":false},"created_at":"2017-11-03T08:28:44Z","updated_at":"2017-11-03T08:28:44Z","author_association":"NONE","body":"The TCP connection drawdown is only one part of the benefit to XNP.  Functionally, CHS now acts like Atrides proxy, which means it makes a single TCP connection, then routes all traffic over that, sending individual logins.  This is auctually worse for a pool, then making large numbers of connections, as you may have multiple thousands of miners on a single TCP connection, which is why you're seeing the slowdowns when making single TCP connections, as you're now locking share validations to a single core, rather than somewhat distributing them.\r\n\r\nAlso, proxies that act like Atrides tend to get packets dropped due to excessive size."}}
{"actor":{"display_login":"Snipa22"}}