Overhead involved with using tcp-store

I'm trying to get a better idea of the overhead involved with using
<tcp-store> in a web application per each request and also across multiple
requests. I plan on doing load-testing and hope to do profiling along with
it. But until I get around to that, I was hoping that one of you could give
me a general idea of what type of overhead I am looking at each time that a
session is stored/saved.
I.E.
Is a new Socket/connection created for each store/save instance?
Obviously there is the overhead of writing the serialized object to file for
both sruns. Is this done asynchronously with the handling of the
request/response?
Any other things that I'm missing?

thanks all,
Miguel Gasca Jr.
Received on Mon 29 Jul 2002 11:38:19 -0700