Forum OpenACS Q&A: Response to Building a high-capacity, high-availability OpenACS solution...

An update on Celebrityblvd.com's situation:
I have installed postgresql, aolserver, and the OpenACS suite on
our production machine here at the office, and everything seems
to be functional.  It was a lot easier than I thought it would be.  :)

We have outsourced all our images and animations to Akamai,
so they will not be served from our machine(s) at all.  It is
currently not feasible for us to expand to more than one machine,
but we are planning on it in the future.  (Speaking of which, how
is load balancing with multiple web servers accomplished, when
you only have one database server?  What are the networking
connections involved?  I've never looked into doing that.)

From the suggestions I've gotten (and thank you, everyone, for
being so helpful!), it seems that upgrading our RAM, to at least
512mb, is the best first step for us, since we have to stick with
our single 650mhz p3 for now.  Our next step will probably be to
get a dual p3/700 with 512mb to 1G of ram, and use that as the
database server.  Will it then be necessary to have a separate
webserver, even though we're not serving any images or
animations (just inital html/tcl/adp requests)?

This could be a big step for the postgres/OpenACS community,
in terms of researching/developing scalability.. I am also working
with the folks who are implementing a Fox movie community site
(quite a big venture) and we're going to attempt an OpenACS
installation, if all goes well with Celebrityblvd.com.  I'll keep you
all updated.  And meanwhile, if anyone knows any creative,
self-starting, intuitive web designers in the Los Angeles
(hollywood) area, send them our way.  :)

Take care, all.