From: Patrick Lauer <patrick@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Monthly Gentoo Council Reminder for August
Date: Thu, 03 Aug 2006 21:22:29 +0200 [thread overview]
Message-ID: <1154632950.24984.80.camel@localhost> (raw)
In-Reply-To: <44D244F2.8030602@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 3167 bytes --]
On Thu, 2006-08-03 at 13:48 -0500, Lance Albertson wrote:
> Patrick Lauer wrote:
>
> > (Note to our sponsors: you rock. Keep on rocking.)
> >
> > Right now bugs is served from a 2,4Ghz P4 - that's roughly a normal
> > desktop box from last year.
>
> You have no concept of where the bottle neck is.
I have followed the discussions quite well. I think I'm quite aware of
the issues.
> The webserver hosting
> the cgi part isn't being loaded hardly at all.
Yes, only problem is that bugzilla likes to consume larger amounts of
memory, and if I'm not mistaken it's a bad interaction from a OOM killer
(to avoid the webfrontend to die) causing stale locks (which should not
happen) that causes bugzie to fall over, ja?
(I've been told a simple testcase to demonstrate that, haven't tried
myself)
> The database server is a
> pretty beefy box, and again, its not so much a specific hardware
> limitation, just more a limitation on the design of bugzilla and its
> ties to mysql. We're having to 'fix' the problem by getting a
> master/slave mysql db server setup which the OSL didn't have setup at
> the time. This is apparently the 'solution' upstream suggests which I
> think is daft, but its what we have to do.
... and one of the slowdowns was OSU being unable to get their DB cluster up and running within a reasonable timeframe. Fertilizer happens ...
> Please stop stating solutions to problems you don't fully understand or
> think you understand. I'm getting tired of all this fud being said
> around about stuff people don't totally understand.
I'm getting tired of being told "we can manage it", then having to wait
6 months to hear "almost there". We had a few people asking how they
could help, and the answer was roughly "we manage fine on our own, thank
you very much". Personally I don't mind much, but then you shouldn't
complain when people say "we could have done better" ...
> Hardware from
> sponsors mean nothing if they aren't utilized in a proper manner with
> planning and skills. And its not really a big bottle neck of people.
That sounds contradictory to me - it's not the people, it's the people?
> You
> try finding people who have a ton of free time, have excellent admin
> skills, gives everyone on the team a 'good vibe' and seems trustworthy.
For me it's easy, being a dev for more than, say, 3 months = trustworthy
Of course if you need to recruit from the outside the situation changes
> Its not as easy as you think it is.
Let me try and fail and I'll believe you ...
> I'm in the process of bringing on a
> guy I know personally which will help the load of things a lot. Plus, he
> works with me, so I can kick him literally if he slacks :). (now if only
> recruiters *cough*swift*cough* could work faster ;-) )
Cool.
> Anyways, I'm not going to rant on about this anymore. We're working on
> the problem, and you just have to be patient.
Nooooooo :-) You said the bad words again! ;-)
I hope you get everything fixed soonish, let's hope Murphy's law doesn't
try to apply here ...
Patrick
--
Stand still, and let the rest of the universe move
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2006-08-03 19:29 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 5:30 [gentoo-dev] Monthly Gentoo Council Reminder for August Mike Frysinger
2006-08-01 11:13 ` Wernfried Haas
2006-08-14 17:23 ` Thierry Carrez
2006-08-15 9:22 ` Stuart Herbert
2006-08-03 9:21 ` Jakub Moc
2006-08-03 12:23 ` Ned Ludd
2006-08-03 13:06 ` Lance Albertson
2006-08-03 13:35 ` Ned Ludd
2006-08-03 14:07 ` Jakub Moc
2006-08-03 14:48 ` Ned Ludd
2006-08-03 15:05 ` Jakub Moc
2006-08-03 13:20 ` Alec Warner
2006-08-03 18:08 ` Patrick Lauer
2006-08-03 18:48 ` Lance Albertson
2006-08-03 19:22 ` Patrick Lauer [this message]
2006-08-04 4:58 ` Jochen Maes
2006-08-03 19:55 ` Chris Bainbridge
2006-08-03 20:54 ` kashani
2006-08-03 21:10 ` Lance Albertson
2006-08-04 8:15 ` Simon Stelling
2006-08-04 13:13 ` Lance Albertson
2006-08-03 20:55 ` Lance Albertson
2006-08-04 5:06 ` Jochen Maes
2006-08-03 18:51 ` Lance Albertson
2006-08-03 19:02 ` Ciaran McCreesh
2006-08-03 19:21 ` Lance Albertson
2006-08-04 5:07 ` Jochen Maes
2006-08-03 17:03 ` Simon Stelling
2006-08-03 17:55 ` Patrick Lauer
2006-08-03 14:58 ` Lance Albertson
2006-08-03 15:10 ` Jakub Moc
2006-08-04 8:57 ` Curtis Napier
2006-08-04 9:07 ` Curtis Napier
[not found] ` <44D34753.6090604@gentoo.org>
2006-08-04 15:53 ` Joshua Jackson
2006-08-04 16:08 ` Alec Warner
2006-08-04 19:23 ` Mike Doty
2006-08-04 18:07 ` kashani
2006-08-04 19:56 ` Robin H. Johnson
[not found] <886253338-1154701653-cardhu_blackberry.rim.net-693078490-@bwe059-cell00.bisx.prod.on.blackberry>
2006-08-04 23:22 ` Matthew Marlowe
-- strict thread matches above, loose matches on Subject: below --
2007-08-01 8:08 Mike Frysinger
2007-08-01 13:14 ` Mike Frysinger
2008-08-01 5:30 Mike Frysinger
2009-08-01 5:30 Mike Frysinger
2009-08-01 13:10 ` Sebastian Pipping
2009-08-02 15:58 ` Denis Dupeyron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1154632950.24984.80.camel@localhost \
--to=patrick@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox