"Roberto T." <r_t@n...> wrote in message
news:OVXEQjzBIHA.4752@T......
> The server load is really low, processor below 10% most of the time.
>
> I use frames in the main web page, so it could be frequent to have
> simultaneous requests from the same client when he arrives to a page with
> frames. I also have a "keepSessionAlive.asp" in a hidden frame, reloading
> automatically every 15 minutes to avoid session timeout (I don't like it,
> but was mandatory).
>
> I have two dictionaries stored in session variables in the main site. They
> are created and populated in the session_on_start function.
> Maybe this is a bottleneck for the server.
>


Absolutely. Use a FreeThreadDOMDocument instead.  If the dictionaries are
holding static info that is common across all sessions consider storing
these DOMs in the Application instead.

Have you considered the cost of building these dictionaries and other
session object variable creation in on_start where the request is coming
from ServerXMLHTTP and hence the built session object will be abandoned
shortly after?  Without the Session.abandon you may well have be consuming a
considerable amount of memory.

An alternative to using Session on start is to abstract access to these
values in a Class placed in an include ASP page.  The class could lazily
create the session variables on demand.  The class could have a property
where the page may indicate that Session variable storage is not required
(because the page is a service expecting to be called by ServerXMLHTTP).


-- 
Anthony Jones - MVP ASP/ASP.NET