Re: [go-nuts] golang thrift server 28k/s request client many dial tcp timeout ,why??

I truely try with two client server to bench it; and the result is the same, so I doubt the performance bottleneck is in the server side but I don't konw the concrete

Re: [go-nuts] golang thrift server 28k/s request client many dial tcp timeout ,why??

Hi! One thing you should check is the amount of TCP sessions you are starting from one host. Since a TCP session is identified by the IP/Port in both ends, and you communicate where some of those numbers stay the same, you are probably limited to no more than 64000 ports at most (or such). If

Re: [go-nuts] golang thrift server 28k/s request client many dial tcp timeout ,why??

I just want to bench the simple server accept new connection now I create a new simple tcp server and use tcp short connection to bench it the result is also that client have many dial i/o timeout does it is client's question ?? 在 2017年6月9日星期五 UTC+8下午9:28:55，Shawn

Re: [go-nuts] golang thrift server 28k/s request client many dial tcp timeout ,why??

client: dial tcp 100.70.186.38:9783: i/o timeout when I modify the server /proc/sys/net/core/netdev_max_backlog16384 /proc/sys/net/core/somaxconn 16384 the client dial timeout decrease some percent 在 2017年6月9日星期五 UTC+8上午12:10:15，Shawn Milochik写道： > > What error are you

Re: [go-nuts] golang thrift server 28k/s request client many dial tcp timeout ,why??

What error are you getting along with the timeout? I suspect that it has something to do with the limit of filehandles on the client. Have a look at this: https://www.cyberciti.biz/faq/linux-increase-the-maximum-number-of-open-files/ -- You received this message because you are subscribed to

[go-nuts] golang thrift server 28k/s request client many dial tcp timeout ,why??

I have a very simple golang thrift server. the handle is very easy just to return But when I use another machine to benchmark the server ,when the qps to 28K/s , client have many dial tcp io/timeout I don't konw the reason ? is the client or server's problem? -- You