Date: Tue, 5 Feb 2013 13:38:28 -0600 From: =?iso-8859-1?Q?Efra=EDn_D=E9ctor?= <efraindector@motumweb.com> To: "Kubilay Kocak" <koobs.freebsd@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: About kern.ipc.somaxconn and netstat Message-ID: <E53693190AA24224BE02F9994B19F1FF@CMOTUM25PC> In-Reply-To: <510A65F5.9070706@gmail.com> References: <BA9FAF0C510840CA9AC80075F227C37E@CMOTUM25PC> <5108E720.70705@gmail.com> <BF1DA7CE551E412E81CBEEA2E0FF84ED@CMOTUM25PC> <510A65F5.9070706@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello. Sorry for the very late answer. That is a very good command, thank you for your recommendation. All the time that I have executed it it shows "0 listen queue overflows" so I guess our configuration is working. Thank you so much. -----Mensaje original----- From: Kubilay Kocak Sent: Thursday, January 31, 2013 6:39 AM To: Efraín Déctor Cc: freebsd-stable@freebsd.org Subject: Re: About kern.ipc.somaxconn and netstat On 31/01/2013 4:54 AM, Efraín Déctor wrote: > -----Mensaje original----- From: Kubilay Kocak > Sent: Wednesday, January 30, 2013 3:25 AM > To: Efraín Déctor > Cc: freebsd-stable@freebsd.org > Subject: Re: About kern.ipc.somaxconn and netstat > > On 30/01/2013 12:26 PM, Efraín Déctor wrote: >> Hello. >> >> We have a webserver using FreeBSD, we read about tunning >> kern.ipc.somaxconn >> (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/configtuning-kernel-limits.html) >> so the OS can handle all the connections. Is there a way to know how >> many connections are established in a certain moment?. I know about >> netstat(1) but is there any other command that we can use to know the >> exact amount of how many connections are established?. >> > This one might help: > > kern.ipc.numopensockets: Number of open sockets > > It's usefulness will depend on the granularity you require (in only, out > only, established only, etc) but it's always represented system-wide > resource consumption very well (matching observed workloads - <some > baseline value>) > > > Thank you, it is very helpfull, using kern.ipc.numopensockets with > sockstat(1) and netstat(1) will give me a clue to tune kern.ipc.somaxconn > > Thank you all. Also, if you haven't already come across this one in your netstat travels, this one directly reports listen queue overflows: netstat -s -p tcp |grep listen -- Ta, Koobs
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E53693190AA24224BE02F9994B19F1FF>