Date: Thu, 4 Oct 2012 15:49:03 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Peter Jeremy <peter@rulingia.com> Cc: freebsd@chrysalisnet.org, freebsd-current@freebsd.org Subject: Re: sysctl kern.ipc.somaxconn limit 65535 why? Message-ID: <CAJ-VmokgRi5fXO4h3LMAUmY0t1QXv=hFF%2B3_0ex-VCiOw3%2Bxtw@mail.gmail.com> In-Reply-To: <20121004222153.GB74702@vps.rulingia.com> References: <03e101cda197$326dc240$974946c0$@org> <20121004222153.GB74702@vps.rulingia.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4 October 2012 15:21, Peter Jeremy <peter@rulingia.com> wrote: > On 2012-Oct-03 19:45:01 +0100, freebsd@chrysalisnet.org wrote: >>In addition we had to migrate all our mysql servers from freebsd to debian >>because they were hitting some arbitary OS limit but I could never figure >>out what, sys% usage went through the roof when this limit was hit, issue >>didnt occur on debian. > > Did you report this issue on any of the FreeBSD mailing lists? > Reporting a problem doesn't guarantee that it will be fixed > (unfortunately) but not reporting a problem makes it extremely > unlikely that it will be fixed. Right, if you don't report that issue then the likelihood of it being fixed is low. It wouldn't be the first time that I've seen FreeBSD expose some bug in some not-quite-right multi-threaded code because it doesn't behave "like linux", regardless of what the specification says. :-) Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmokgRi5fXO4h3LMAUmY0t1QXv=hFF%2B3_0ex-VCiOw3%2Bxtw>