|
Joseph Mack wrote:
> All this is speculation and can be revised in the face of more evidence.
> Do you find that you can't retrieve the gif sometimes? What if you refresh
> n times where n is the number of real-servers, do you eventually get
> the gif?
>
I have not tested it yet (not ported the CGIs yet to the new LVS box)
but I think
things are not so simple.
In a 'rr' scheduling configuration, for example, the scheduler
could play dirty, depending on the number of http requests for the
given page,
and the number of realservers. Both could be incommensurable in a way
that the
http request for the GIF never reaches the same realserver as the one
which ran the
CGI request.
But my original question was only theoretical. I had already decided
beforehand
that I need shared directories between all real servers for our CGI
environment
which does computationally expensive things all the time. It is not
only dynamically
created givs, some CGIs create also data files which are used by later
CGIs.
It is either shared directories for such files, or a shared database
(which we
also use).
These temp files will be sitting in the RAM cache of the NFS server,
so that only
network bandwidth between the realservers and the NFS server is the
limiting
factor. This is why I give the NFS server 2 gb of RAM, the max. it
will physically
take, and this is why I chose 2.2.19 as the kernel because it contains
NFS-3, which
is said to be faster than NFS-2.
Alois
--
|| Alois Treindl, Astrodienst AG, mailto:alois@xxxxxxxxx
|| Zollikon/Zurich, Switzerland
|
