From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1G921u-00081y-4N for garchives@archives.gentoo.org; Fri, 04 Aug 2006 15:56:06 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.7/8.13.6) with SMTP id k74FtHhL014511; Fri, 4 Aug 2006 15:55:17 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by robin.gentoo.org (8.13.7/8.13.6) with ESMTP id k74FrLl9024638 for ; Fri, 4 Aug 2006 15:53:21 GMT Received: from [10.99.0.1] (adsl-71-158-135-138.dsl.renocs.sbcglobal.net [71.158.135.138]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 8C72A649FA for ; Fri, 4 Aug 2006 15:53:20 +0000 (UTC) Message-ID: <44D36D6E.3060705@gentoo.org> Date: Fri, 04 Aug 2006 08:53:18 -0700 From: Joshua Jackson User-Agent: Thunderbird 1.5.0.5 (X11/20060730) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Monthly Gentoo Council Reminder for August References: <20060801093001.C97C864465@smtp.gentoo.org> <44D1BFFD.4040303@gentoo.org> <1154607828.23292.5.camel@localhost> <44D1F4EF.3000209@gentoo.org> <1154612153.17538.26.camel@onyx> <44D30BE8.8060909@gentoo.org> <44D34753.6090604@gentoo.org> In-Reply-To: <44D34753.6090604@gentoo.org> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: f5f55a35-67e1-4d35-8be9-2ea751caa283 X-Archives-Hash: c379fb079df08b358c8459ef8e1cfef0 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Lance Albertson wrote: > Curtis Napier wrote: > >> I got to chat with the CEO of the company that donated that equipment >> and the wait was *more* than worth it. Once it's up and running our >> bugzilla will be rock solid and fast fast fast fast fast for years to come. > > Well, as I stated before. Having nice hardware will help a lot, but if > we could get upstream bugzilla folks to fix some of these issues instead > of us having to resort to a clustered database structure would be the > better solution in the long run. A fast db cluster/web server means > nothing if the database structure behind the app isn't done properly. It > might be worth it for someone to maybe look at the problem in the code > and see if we can patch it from our end and then submit those patches > upstream. That approach generally works better. But I fear that the > change needed to be done on it might involve so much change/work, it may > not be worth it. Who knows, maybe its worth finding another bug database > app, or even be crazy and write our own for a long term solution. > > Cheers- > Here's the question, gnome's bugzilla has over twice as many bugs as we have, is quite speedy and doesn't seem to suffer from the OOM killers that our bugzilla has. So what's the difference? Did gnome just toss hardware at the problem to make it go away or have they done something to make bugzilla work for them? I think throwing hardware at the problem is the wrong approach in this case, as its just delaying the problem that has made the new hardware seem like the solution...which will no doubt creep up again. Don't get me wrong, the donation of hardware from gni is greatly appreciated. I'd just to see that we try and see why we have the problem in the first place as well. As I'm sure that this problem will creep up again -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE021uSENan+PfizARAifIAKCQ1g0sVRxvAbpm1khTCLfw9KxOTgCcD1lo 6Arc6MGKDoqRTfZWgvWR1fQ= =5gzO -----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list