Date: Sat, 27 Mar 2004 18:40:21 +0300 (MSK) From: Igor Sysoev <is@rambler-co.ru> To: Kevin Day <toasty@dragondata.com> Cc: freebsd-net@freebsd.org Subject: Re: sendfile returning ENOTCONN under heavy load Message-ID: <Pine.BSF.4.21.0403271838020.6519-100000@is> In-Reply-To: <23E302EC-7F7F-11D8-AA0F-000A95A8A1F2@dragondata.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 26 Mar 2004, Kevin Day wrote: > I'm using thttpd on a server that pushes 300-400mbps of static content, > using sendfile(2). > > Once the load reaches a certain point (around 800-1000 clients > downloading, anywhere from 150-250mbps), sendfile() will start randomly > returning ENOTCONN, and the client is disconnected. I've raised > kern.ipc.nsfbufs pretty high and that hasn't made any difference. Is > there any easy way to tell exactly why the sockets are being closed? I > can't seem to find any obvious signs of memory exhaustion or anything. It's the sendfile(2) feature. It can return ENOTCONN instead EPIPE. See the message: http://freebsd.rambler.ru/bsdmail/freebsd-hackers_2004/msg00019.html and its follow-ups. Igor Sysoev http://sysoev.ru/en/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0403271838020.6519-100000>