Date: Fri, 5 Oct 2012 07:11:16 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Ivan Voras <ivoras@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: sysctl kern.ipc.somaxconn limit 65535 why? Message-ID: <CAJ-VmomJMDAn_D408Ze4FV5tN3gpnboMFQvDSGdyHoBSm%2BPXmw@mail.gmail.com> In-Reply-To: <k4mjlp$nn5$1@ger.gmane.org> References: <03e101cda197$326dc240$974946c0$@org> <CAJ-Vmo=CtC1SpsedP3nHJsrApTLzktGrjopeV0vXShr0FOUsmA@mail.gmail.com> <506C9CE4.6080400@freebsd.org> <k4mjlp$nn5$1@ger.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5 October 2012 05:26, Ivan Voras <ivoras@freebsd.org> wrote: > On 03/10/2012 22:15, Andre Oppermann wrote: > >> I guess the problem is rather kern.ipc.maxsockets which is only 25600. > >> maxsockets should be bumped up quite a bit by default IMO. How far needs >> some analysis because there are some dependencies and memory >> requirements. > > So, how about a heuristic, 20,000 + (5000 for every GB of RAM)? > > A small, 16 GB machine (yes, 16 GB is "small" nowadays) would have > 100,000, which should be enough. Well, it depends on what the server is being used for, right? If it's a small object proxy/web server sure. But if it's a streaming server you may only need a few thousand sockets but very deep send buffers. Honestly, I'd really like the OP to come to us with workloads that aren't working and get them fixed. We're a pretty smart bunch over here and it's highly likely that both he and we would learn from the process. :) And double honestly, it may be nice to print out a "running out of sockets!" warning, as well as a "running out of mbufs!" warning. Rate limited, so people don't get spammed. But a gentle notification that they should retune some stuff would be user-friendly. Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmomJMDAn_D408Ze4FV5tN3gpnboMFQvDSGdyHoBSm%2BPXmw>