From owner-freebsd-performance@FreeBSD.ORG Mon Jan 2 01:28:08 2006 Return-Path: X-Original-To: freebsd-performance@freebsd.org Delivered-To: freebsd-performance@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E60C16A41F for ; Mon, 2 Jan 2006 01:28:08 +0000 (GMT) (envelope-from chrcoluk@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D73C43D45 for ; Mon, 2 Jan 2006 01:28:07 +0000 (GMT) (envelope-from chrcoluk@gmail.com) Received: by wproxy.gmail.com with SMTP id i31so2066970wra for ; Sun, 01 Jan 2006 17:28:07 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=NgepDokK6je7qf0M8XfiVmNLTfoXDIX3jvq9DY/2X/1YGVCuQ2aLKDImWyd+CyE0Xq4J6qPxhGoqTlqzx6dapR3tc4OG9xHlZ8l8O7fSOTofQPPmwyID4F/CopPIplL4a/TP3K7FE649fdbOoWeP90UL5YYqUZSQ9GJLt+b8YB0= Received: by 10.54.102.6 with SMTP id z6mr348368wrb; Sun, 01 Jan 2006 17:28:07 -0800 (PST) Received: by 10.54.122.17 with HTTP; Sun, 1 Jan 2006 17:28:07 -0800 (PST) Message-ID: <3aaaa3a0601011728j31f1cd5as@mail.gmail.com> Date: Mon, 2 Jan 2006 01:28:07 +0000 From: Chris To: Michael Vince In-Reply-To: <43B7BBEE.5020701@roq.com> MIME-Version: 1.0 References: <43B7BBEE.5020701@roq.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-performance@freebsd.org, huang leo Subject: Re: Benchmark MySQL Performance On FreeBSD And Linux X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 01:28:08 -0000 On 01/01/06, Michael Vince wrote: > > huang leo wrote: > > >Hi, all: > > > >We had evaluated MySQL performance on FreeBSD and Linux. The result is > >attached. > > > >We are longing for your feedbacks! > > > > > >Best regards, > > > >Leo Huang > > > Really good work. > > I gave your results some thought and was thinking that maybe you should > check to see if you reached the default 1500 threading limit of libthr > and maybe it needs to be increased, I set mine to 40000 like below. > kern.threads.max_threads_per_proc=3D40000 > kern.threads.max_groups_per_proc=3D40000 > > I was thinking it would be good to show threading usage activity with > some kind of 1 second loop doing ps -auxwH | grep -c 'mysql' or > something like that so we could see what limits its getting to, and so I > can have an idea of what I can compare it to on my own servers. > > Just a suggestion. > > Regards, > Mike Well sorry if I am completely wrong here, but that test seems to indicate there is a general stability problem with libpthread. My own experience backs up their results since on a production web server with heavy forums I have had mysql lockups until I tinkered with the threading settings. Libthr is the good old threading routine from the 4.x days if I am correct, so if libpthread is indeed unstable under continous heavy load how has it become unoticed by the developer's or has it just been tested in desktop environments? If libpthread is a problem is it maybe better to further develop libthr or at least add a option in the mysql ports Makefile to allo= w users to use it without tinking with libmap.conf manually. I understand that libpthread is mainly an advantage for SMP systems but if (a) it introduces instability the increased performance it gives becomes irrelevan= t and (b) what about UP systems what is the best threading routine for them? libthr has that been improved in 5.x since 4.x as their results did show libthr was better then linuxthreads when in the 4.x days linuxthreads was considered better. I am confused now as their is very little documentation on this, google throws up barely anything and my main concern is stability. Chris