"Jeffrey W. Baker" wrote:
>
> >
> > With sharing state files to an NFS share, the sessions can move
> > from server to server even if one server goes offline, which
> > you won't find with solutions that have clients stay on a server
> > saving session data locally in RAM or disk.
>
> On my sites I use a central database for storing the session objects, and
> all of the https servers access this central resource. Obviously if it
> goes down, everything is toast, but the same can be said of the database
> that stores all of the customer information, etc.
>
How many writes and session ties per second does this system
handle, and what kind of db are you using. Currently the NetApp
NFS file sharing approach seems to max out around 40 Apache::ASP
style session creations per second. This involves writing to a
central internal session for session tracking, and the creation of
the relevant db files.
I ask because I'm looking at going with your approach to handle greater
loads, and wondering where you max out at with MySQL/Oracle (?), & what
kind of hardware you are running.
-- Joshua
