From: "Daniel Berlin" <dberlin@dberlin.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: overseers@gcc.gnu.org
Subject: Re: Bugzilla 3.0 and mod_perl
Date: Sat, 02 Jun 2007 02:13:00 -0000 [thread overview]
Message-ID: <4aca3dc20706011913k2acc4bedhed4cf223e8150b94@mail.gmail.com> (raw)
In-Reply-To: <20070531172753.GD3094@redhat.com>
On 5/31/07, Frank Ch. Eigler <fche@redhat.com> wrote:
> HI -
>
> > I'm going to be upgrading our bugzilla installs to 3.0 in a few weeks
>
> Great.
>
> > One of the nicer features is that you can run multiple db's from one
> > bugzilla install, so i can eliminate the need for the two copies we
> > have now.
>
> Coincidentally, would it make sense to move the mysql server over to
> server2? How much database traffic is there?
We average about 47 queries per second, however over the course of 30
million queries, only 15 have shown up as being "slow".
The default is that any query taking longer than 1 second is
considered slow. So i don't think we are having that much issue with
mysql speed or load :)
Uptime: 638886 Threads: 1 Questions: 30021162 Slow queries: 15
Opens: 183 Flush tables: 1 Open tables: 177 Queries per second avg:
46.990
>
> > Bugzilla 3.0 also supports running under mod_perl. Under mod_perl,
> > the cpu usage is *greatly* decreased, but the memory usage is
> > heavily increased [100-200 MB]
>
> If that's per-httpd-process, then it's obviously too much.
It is, AFAIK. It is shared among threads/children, but not separate processes.
> If it's
> shared amongst the httpd's, it should be OK. Any idea what would take
> up all that memory though?
>
God only knows, since it's perl :)
I ust know what the bugzilla release notes say.
I haven't tried it.
> - FChE
>
prev parent reply other threads:[~2007-06-02 2:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 13:25 Daniel Berlin
2007-05-31 17:28 ` Frank Ch. Eigler
2007-05-31 17:52 ` Christopher Faylor
2007-06-02 2:13 ` Daniel Berlin [this message]
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=4aca3dc20706011913k2acc4bedhed4cf223e8150b94@mail.gmail.com \
--to=dberlin@dberlin.org \
--cc=fche@redhat.com \
--cc=overseers@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).