From owner-freebsd-current@FreeBSD.ORG Sun May 23 12:23:48 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D76016A4CE for ; Sun, 23 May 2004 12:23:48 -0700 (PDT) Received: from mail.mikehost.net (lvs-1.voxel.net [207.99.115.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7154343D39 for ; Sun, 23 May 2004 12:23:48 -0700 (PDT) (envelope-from mike@mike2k.com) Received: by mail.mikehost.net (Postfix, from userid 502) id 0A7011BC7D; Sun, 23 May 2004 12:23:44 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.mikehost.net (Postfix) with ESMTP id 081DF1BC7A for ; Sun, 23 May 2004 12:23:44 -0700 (PDT) Date: Sun, 23 May 2004 12:23:44 -0700 (PDT) From: mike X-X-Sender: mike@sql01.internal.mikehost.net To: freebsd-current@freebsd.org Message-ID: mike: yes MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Mon, 24 May 2004 04:46:09 -0700 Subject: Re: Why is MySQL nearly twice as fast on Linux? (fwd) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 May 2004 19:23:48 -0000 i'm sending this to the -current list as well. it seems nobody wants to help take ownership - and i'm trying to get some sort of incentive going. i know there are other people out there who can probably contribute more as well if this can be fixed/resolved. [please read my reply below] - mike ---------- Forwarded message ---------- Date: Sun, 23 May 2004 12:21:42 -0700 (PDT) From: mike To: freebsd-threads@freebsd.org Subject: Re: Why is MySQL nearly twice as fast on Linux? On Sun, 23 May 2004, Ivan Voras wrote: > > The worst thing is, this is not a new problem - various users have > reported performance troubles with libpthread and/or mysql, including at > this thread in freebsd-current: > once again, here's the deal. i'm willing to PAY someone to own this issue and figure out how to resolve it. also give them access to my box to do whatever they feel like (it needs to stay AMD64 - but i don't care if you go up to 5.3, down to 5.2-current, 5.1, whatever) so i'm supplying resources and incentive. why is nobody stepping up to the plate to help figure out where the bottleneck is? it *sounds* like it's threading or the scheduler or a combination of both, i don't know. but i'm pledging at least $250 USD, and someone else will pledge another $100 - and that's just two of us. if someone owns it and can get a fix out in the next week or two (i don't care how or where) i could even give a bonus. once again - resources and incentive. let's figure this out so everyone can benefit. i just want to expedite this effort.