public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Daniel Berlin" <dberlin@dberlin.org>
To: overseers@gcc.gnu.org
Subject: Bugzilla 3.0 and mod_perl
Date: Thu, 31 May 2007 13:25:00 -0000	[thread overview]
Message-ID: <4aca3dc20705310625s399ecf9flc16557a015b027f3@mail.gmail.com> (raw)

I'm going to be upgrading our bugzilla installs to 3.0 in a few weeks

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.

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.

My guess is that it would take 100-200 meg of memory in process in our httpds.

I'm not sure whether this is a good tradeoff for us.

Thoughts?

             reply	other threads:[~2007-05-31 13:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-31 13:25 Daniel Berlin [this message]
2007-05-31 17:28 ` Frank Ch. Eigler
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=4aca3dc20705310625s399ecf9flc16557a015b027f3@mail.gmail.com \
    --to=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).