-
Notifications
You must be signed in to change notification settings - Fork 325
连接页面的连接超过3000就卡成皮皮虾,难道只有我一个人这样吗? #1277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
试试zashboard那个似乎有优化 |
谢谢。试过了。。一样卡成皮皮虾。。哈哈 |
15000个连接感觉确实太多了,你可以试试把直连的提前绕过核心? |
额。。没有什么直连。只是做了dialer-proxy链式。所以会有很多被识别成直连。 我这还是做了两台分开来跑。。。用一台跑会到3W连接。。。更卡。 连接在3000以下可以勉强等等会刷出来。。超过3000那就要刷半天才刷都出来。 |
同,把连接页面丢在单独的显示器做连接的监控用,结果每次都是连接数上来爆炸卡,内存吃满。刷新页面也无效,必须关掉标签页之后重新打开。 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
连接超过3000的时候,基本就各种 无响应 崩溃都来了。。。
像我这样超过一万连接的。。那页面没半个小时基本是看不了一点。
能优化一下吗。或者怎么默认以源地址来收缩打开来缓解一下。。。
The text was updated successfully, but these errors were encountered: