> For load balancing.
But still, you can do that easily with rewrite rules and proxying. Can
you explain the advantage of using FastCGI?
> Now, here comes another question, if there's many
> request per seconds, ie., high load, what is best deployment strategy
> for this?
As you said, the strategy is to do a per-session load balancing onto
multiple images. I think a good guideline is to have one CPU and 1 GB
of RAM for each image, but that might also depend on your persistency
backend.
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch