From: Jeffrey A Law <law@redhat.com>
To: Phil Edwards <pedwards@disaster.jaj.com>
Cc: overseers@sources.redhat.com
Subject: Re: splitting sourceware into pieces?
Date: Wed, 21 Feb 2001 14:31:00 -0000 [thread overview]
Message-ID: <5376.982792391@slagheap.cygnus.com> (raw)
In-Reply-To: <20010221142147.A20931@disaster.jaj.com>
In message < 20010221142147.A20931@disaster.jaj.com >you write:
> Not the physical machine, but rather its functionality. (Y'all can resume
> breathing now. :-)
>
> During the middle of the day, mail seems to be taking upwards of half an
> hour to get processed by the lists; CVS connections can be dog slow for
> anyone who has less than an OC-3, etc, etc, you all have heard this before.
> How about delgating email to one machine and everything else to another?
> Or maybe FTP and web traffic to one machine, and everything else to another
> .
> You get the picture; it doesn't need to all be on one system.
>
> Maybe this is a completely pointless idea considering the upcoming co-loc.
We're mostly concerned with getting ready for moving to the co-loc;
as part of that move we're purchasing a new machine, roughly 2X the
performance of the current box which should help a lot.
jeff
prev parent reply other threads:[~2001-02-21 14:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-21 11:10 Phil Edwards
2001-02-21 12:51 ` Andrew Cagney
2001-02-21 14:28 ` Jason Molenda
2001-02-21 14:41 ` Phil Edwards
2001-02-21 15:27 ` Jason Molenda
2001-02-21 13:06 ` Jason Molenda
2001-02-21 13:16 ` Jason Molenda
2001-02-21 13:22 ` Phil Edwards
2001-02-26 8:43 ` Jeffrey A Law
2001-02-21 14:31 ` Jeffrey A Law [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=5376.982792391@slagheap.cygnus.com \
--to=law@redhat.com \
--cc=overseers@sources.redhat.com \
--cc=pedwards@disaster.jaj.com \
/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).