You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using goproxy as a dependency in my proxy pool to maintain proxies for multiple IP agents
Possible Solution
When the request volume is high, goproxy can suddenly fill up the computer's CPU and memory. I don't know what the problem is, but I checked the code and it seems that there is no limit to the number of coroutines? Is it still a problem with TLS certificate encryption and decryption? Can configurable optimizations be added if possible?
Yes, this is also the case on my side. Today, I pressed the goproxy service, and once it was https interface proxy, 200qps, it directly exploded. I hope to solve this problem as soon as possible
Expected Behavior
Current Behavior
I am using goproxy as a dependency in my proxy pool to maintain proxies for multiple IP agents
Possible Solution
When the request volume is high, goproxy can suddenly fill up the computer's CPU and memory. I don't know what the problem is, but I checked the code and it seems that there is no limit to the number of coroutines? Is it still a problem with TLS certificate encryption and decryption? Can configurable optimizations be added if possible?
Steps to Reproduce
https://github.com/windfgg/ProxyPool
Context (Environment)
Detailed Description
Are you considering this optimization? Or provide a solution?
Possible Implementation
The text was updated successfully, but these errors were encountered: