From owner-freebsd-threads@FreeBSD.ORG Wed Jun 16 04:49:24 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 C696816A4CE for ; Wed, 16 Jun 2004 04:49:24 +0000 (GMT) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8330843D2F for ; Wed, 16 Jun 2004 04:49:24 +0000 (GMT) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (sccrmhc13) with ESMTP id <200406160449230160083bjte>; Wed, 16 Jun 2004 04:49:23 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id VAA54442; Tue, 15 Jun 2004 21:49:21 -0700 (PDT) Date: Tue, 15 Jun 2004 21:49:20 -0700 (PDT) From: Julian Elischer To: JG In-Reply-To: <5.2.0.9.2.20040615210256.016c55e0@mail.ojoink.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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: Wed, 16 Jun 2004 04:49:24 -0000 but you can run systat -vmstat when it is as fast as it can go... and you can do teh ktrace (man ktrace) and make the file available... :-) On Tue, 15 Jun 2004, JG wrote: > > > > >erk! :-) > > > >As I suggested elsewhere: > >----- quoted---- > > > >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 > > > Julian, > > I think I'll wait for someone more qualified to evaluate these problems. > > I can't code, don't have commit access, and don't even know how to see > what was added or removed to -CURRENT when or where etc. > > The problem has been laid on the table of the FreeBSD gods by many > people now. FreeBSD would be dead in the water if it relied on the likes > of me to do assessments and debugging. > > Once I identified what was taking too long and what was waiting on what > - I would have no clue what to do or try from there, but I'm sure it would > require some coding experience. > > - Jeremy > > > > > _______________________________________________ > freebsd-threads@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-threads > To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd.org" >