[go-nuts] Re: dial io timeout and tcp short connection performance bottleneck
Are you exhausting the local TCP sockets? Some (50k?) in a wait state? Try using a few IP addresses on the test box. Increase /proc/sys/net/core/somaxconn to a larger value, if you have a 20 millisecond pause at 28kreqs/sec then thats 500 ish connections so 1024 may not be enough. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[go-nuts] Re: dial io timeout and tcp short connection performance bottleneck
I meant the fully open connections waiting for application handling so the listen queue (somaxconn). On the client and server I'd check you aren't exhausting any of the more obvious limits, so ports/listen queues. Adding more virtual IPs is easy way to test the ports. Listen queues should show up in "netstat -s" as TPC drops. Increasing somaxconn should help unless you are CPU/network limited. It's very easy to hit a system limit and then think your programming is at fault. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
