From: "Frank Ch. Eigler" <fche@redhat.com>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: overseers@gcc.gnu.org
Subject: Re: Bugzilla 3.0 and mod_perl
Date: Thu, 31 May 2007 17:28:00 -0000 [thread overview]
Message-ID: <20070531172753.GD3094@redhat.com> (raw)
In-Reply-To: <4aca3dc20705310625s399ecf9flc16557a015b027f3@mail.gmail.com>
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?
> 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. If it's
shared amongst the httpd's, it should be OK. Any idea what would take
up all that memory though?
- FChE
next prev parent reply other threads:[~2007-05-31 17:28 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 [this message]
2007-05-31 17:52 ` Christopher Faylor
2007-06-02 2:13 ` Daniel Berlin
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=20070531172753.GD3094@redhat.com \
--to=fche@redhat.com \
--cc=dberlin@dberlin.org \
--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).