Date: Wed, 4 Jan 2012 16:49:50 -0500 From: Arnaud Lacombe <lacombar@gmail.com> To: Chuck Swiger <cswiger@mac.com> Cc: freebsd-current@freebsd.org, Dan The Man <dan@sunsaturn.com> Subject: Re: sysctl kern.ipc.somaxconn limit 65535 why? Message-ID: <CACqU3MULYpULrX6CiCOwim3hwO7cbGdiRm7apJ_GOtJLY5gFNA@mail.gmail.com> In-Reply-To: <AC03F2F8-92AD-4520-BFCB-AA29AA18FF4D@mac.com> References: <alpine.BSF.2.00.1201041419340.4843@sunsaturn.com> <0A9B7C39-DFA9-4C65-BE39-CC72E18DAB87@mac.com> <alpine.BSF.2.00.1201041439080.4843@sunsaturn.com> <52A4B11E-592E-458D-BA0F-9B5A349F4B73@mac.com> <alpine.BSF.2.00.1201041456300.4843@sunsaturn.com> <AC03F2F8-92AD-4520-BFCB-AA29AA18FF4D@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Wed, Jan 4, 2012 at 4:42 PM, Chuck Swiger <cswiger@mac.com> wrote: > On Jan 4, 2012, at 1:03 PM, Dan The Man wrote: >>> However, I'm not convinced that it is useful to do this. =A0At some poi= nt, you are better off timing out and retrying via exponential backoff than= you are queuing hundreds of thousands of connections in the hopes that the= y will eventually be serviced by something sometime considerably later. >> >> I agree completely, in practical application this makes sense, but why s= hould the OS dictate not being able to temporarily set that setting higher = in order to fully benchmark the application at 100k+ in the listen queue if= the developer so chooses? I think that alone should be a good reason, to m= ake freebsd developer friendly. > > The job of the OS is to manage resources on behalf of the users and proce= sses using the system. > No. The job of the OS is to service the user with the resource available, not constrict the user within some arbitrary predefined wall when there is still plenty of room available. If resource become scarce, then take action. > Some developers feel that VM means that the system should always claim ha= ve more memory available, but always saying "yes" isn't "managing resources= ". =A0I'd rather have the OS return a null pointer and set ENOMEM when some= one tries to malloc() more memory than the system (including swap, VM overc= ommit, etc) has, and I expect developers to code well enough to handle mall= oc() failures. > this is merely a policy issue, not yours to impose. > Setting the listen queue to an arbitrarily high value isn't useful, and d= evelopers would be better advised to pay attention to best practices in the= face of a massive connection backlog. > Stress-testing isn't about "best practice". It is about shaking enough the system to highlight weak point. - Arnaud > Regards, > -- > -Chuck > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= "
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACqU3MULYpULrX6CiCOwim3hwO7cbGdiRm7apJ_GOtJLY5gFNA>