We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It might be a good idea to do some tuning of the system (mostly network) for apps with lots of concurrent connections.
This is mostly important for the portal instance: net.ipv4.tcp_rfc1337 = 1 net.ipv4.tcp_tw_reuse = 1 net.ipv4.ip_local_port_range = 1024 65535
maybe a few more options? https://easyengine.io/tutorials/linux/sysctl-conf/ https://wiki.ubuntu.com/ImprovedNetworking/KernelSecuritySettings
The text was updated successfully, but these errors were encountered:
it looks like tcp_tw_reuse only matters for connections initiated by the server, so from portal to backend nodes, and doesn't really do much for connections to clients connecting to portal. https://vincent.bernat.ch/en/blog/2014-tcp-time-wait-state-linux#summary
Sorry, something went wrong.
No branches or pull requests
It might be a good idea to do some tuning of the system (mostly network) for apps with lots of concurrent connections.
This is mostly important for the portal instance:
net.ipv4.tcp_rfc1337 = 1
net.ipv4.tcp_tw_reuse = 1
net.ipv4.ip_local_port_range = 1024 65535
maybe a few more options?
https://easyengine.io/tutorials/linux/sysctl-conf/
https://wiki.ubuntu.com/ImprovedNetworking/KernelSecuritySettings
The text was updated successfully, but these errors were encountered: