I've been dealing with this issue privately with a few folks, so I don't
know that discussion on it belongs on the public discussion forum, but
since it was brought here I'll continue it here.
The biggest bottleneck is I/O. I indicated to Mike Pogue that a RAID
array would be the biggest, immediate help. It sounds like that might be
a problem, though.
Second problem regarding upgrading is that there is no more adjacent space
in the rack where Taz is sitting. There hasn't been in a long time - rack
space at above.net is at a premium. So to expand or move to a new system
involves either completely replacing taz (a completely nontrivial
operation) or moving to a new system.
The good news is that I have a new system in my hands. Rack-mount dual
PII450, 512MB of memory, two 18G U2W disks, FreeBSD 3.3 already installed,
etc. I have rack space at Level3 (a peer to above.net). I am very close
to getting that online - the issue there is that we're moving to a larger
IP space, so I don't want to bring anything new online before we make that
switch. That *should* happen towards the end of this week or the
beginning of next, but you know how IP provisioning goes. I'm also at
Comdex right now so I can't do much work on it in the short term.
I can still use a RAID system as I mentioned to Mike Pogue a few weeks
back. If someone else can recommend external rack-mount slender RAID
solutions that work with FreeBSD, I'm all ears. But that shouldn't be a
blocking factor to bringing a new system online.
In the meantime, I've given Pier info on how to address the I/O
bottlenecks that gather on taz from time to time.
Brian
On Mon, 15 Nov 1999 [EMAIL PROTECTED] wrote:
> Taz appears to be pretty badly overloaded. Access to the CVS repository
> tends to be slow, both for updates and commits. It's getting to be a bit
> of a problem, so we need to decide on the best way to fix it.
>
> We could look at
>
> o Upgrading Taz. RAID disks, more memory, faster CPUs, whatever.
>
> o Partitioning the load. Taz is handling a lot of stuff; perhaps
> moving all of the Apache XML stuff (CVS, web server, mailing lists)
> to their own machine would make sense. Or it could be split
> based on function rather than project, with CVS, mail and web
> serving on separate machines, but with each handling all of the
> projects.
>
> o Some way of running local CVSs that mirror the main one on Taz.
>
> Any other ideas? Or thoughts on how best to make it happen?
>
> -- Andy Heninger
>
>
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Collab.Net is hiring! http://www.collab.net/
