From owner-freebsd-threads@FreeBSD.ORG Tue Jun 15 23:21:08 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7634316A4CF; Tue, 15 Jun 2004 23:21:08 +0000 (GMT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6865143D5C; Tue, 15 Jun 2004 23:21:08 +0000 (GMT) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (rwcrmhc13) with ESMTP id <2004061523204001500ff6e3e>; Tue, 15 Jun 2004 23:20:51 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id QAA50750; Tue, 15 Jun 2004 16:20:39 -0700 (PDT) Date: Tue, 15 Jun 2004 16:20:38 -0700 (PDT) From: Julian Elischer To: mike In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org cc: freebsd-threads@freebsd.org Subject: Re: Possible Threading problem with -CURRENT / MySQL? X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jun 2004 23:21:08 -0000 On Mon, 14 Jun 2004, mike wrote: > welcome to our hell. we've been experiencing mysql problems on freebsd 5.x > as well. it sounds like scheduler/threading is to blame but we were not > able to give sufficient or proper motivation to the folks who could > examine this deeper - we even offered $500 cash to whomever stepped up to > help resolve this. > > linux runs almost 2x as fast on the same hardware with no configuring - > and we get nearly the same results running in single CPU mode vs. dual CPU > mode on fbsd... something is definately fubar with the mysql+fbsd5.x > combination. > > You complained about this some time ago and you have still not responded with the information I suggest.. ---- quote from my previous mail--------------- I'm not saying I can help particularly but the problem is that the people who can help are generally not interested in databases.. what needs to happen is for some analysis to be made as to where the time is being spent.. I vaguely remember you saying htat teh cpu was not piegged when you had this problem... You didn't indicate whether the disks were at 100%. to check this you should try running systat -vmstat while noticing the slowdown and try see what is at 100%. if it turns out that you are NOT seeing disk or CPU limitted then the next step would be to take a snapshot of operations using ktrace -d -p (pid) for 20 second followe by krtace -C to turn it off again. then looking at the output may give an idea of what operations are taking too long, and what is waiting on what.. ---------------------------------------------- Julian