Re: user sessions eating all my ram

"Scott" wrote in message
news:e8Q6oCszHHA.3788@TK2MSFTNGP02.phx.gbl...
> Hi.
>
> Im having problems with user sessions on IIS6 eating all my ram. Each
> w3wp.exe*32 service is consuling 30-40 mb .... and hurting other apps.
>
> Im have already restricting default app pool cpu usage, session numbers,
> recycle every 60 mins,.
>
> Any thing else i can do ?

Hi,

Is this classic ASP? What are they storing in the session?

--
Session Replacement for ASP and ASP.NET
http://www.nieropwebconsult.nl/asp_session_manager.htm

> Cheers
> Scott
>

user sessions eating all my ram

Hi.

Im having problems with user sessions on IIS6 eating all my ram. Each
w3wp.exe*32 service is consuling 30-40 mb .... and hurting other apps.

Im have already restricting default app pool cpu usage, session numbers,
recycle every 60 mins,.

Any thing else i can do ?

Cheers
Scott

Re: user sessions eating all my ram

whatever it does by default i guess ... i dont actually know. our app doesnt
do anything on purpose. I stores xml locally and cookie on user pc.

Re: user sessions eating all my ram

its ASP 2 btw

Re: user sessions eating all my ram

its crazy everytime i connect a browser to the site a new w3wp.exe process
is created and 40 mb ram allocated .... i then close the browser and the
process is still there with the 40mb still allocated.

Re: user sessions eating all my ram

"Scott" schreef in bericht
news:uWgEcdszHHA.5408@TK2MSFTNGP02.phx.gbl...
> its crazy everytime i connect a browser to the site a new w3wp.exe process
> is created and 40 mb ram allocated .... i then close the browser and the
> process is still there with the 40mb still allocated.

Don't assume I or somebody can guess what's happening.
Is there any reason you need to run it in 32bit mode while on a x64 windows
edition? I guess, you are using some specific COM component.

If possible, tell us what the app does. Which 'createobjects' to what
progids are being used?

Re: user sessions eating all my ram

thanks for the reply and sorry for lack of detail.

"Is there any reason you need to run it in 32bit mode while on a x64 windows
edition? "
thats what it does by default, app compiled for 32bit cpu

"If possible, tell us what the app does. Which 'createobjects' to what
progids are being used?"
Its a really simple form based index page at the stage where the ram is
allocated. When connecting to the site as anon user (before app
authentication) a w3wp.exe process is created with 30 - 40 mb ram allocated.
App uses asp.net (32bit) extension. Our app does nothing at this stage at
all . The ram is getting allocated by default by ASP or IIS , we just have a
form as an index page thats it !.... app uses session cookies but not at
this stage ... server just displays the tiny index page (with simple login
box) and it takes all that memory. I have talked to the programmers and they
have no influnece over this at the moment , dont tweak the environment at
all.

I think this problem is to do with the configuration of ASP.net 2
environment, my default application pool, or iis6.

Thanks again for your time
Scott

Re: user sessions eating all my ram

"Scott" wrote in message
news:Oo9Chj2zHHA.3536@TK2MSFTNGP06.phx.gbl...
> thanks for the reply and sorry for lack of detail.
>
> "Is there any reason you need to run it in 32bit mode while on a x64
> windows edition? "
> thats what it does by default, app compiled for 32bit cpu
>
> "If possible, tell us what the app does. Which 'createobjects' to what
> progids are being used?"
> Its a really simple form based index page at the stage where the ram is
> allocated. When connecting to the site as anon user (before app
> authentication) a w3wp.exe process is created with 30 - 40 mb ram
> allocated. App uses asp.net (32bit) extension. Our app does nothing at
> this stage at all . The ram is getting allocated by default by ASP or IIS
> , we just have a form as an index page thats it !.... app uses session
> cookies but not at this stage ... server just displays the tiny index page
> (with simple login box) and it takes all that memory. I have talked to the
> programmers and they have no influnece over this at the moment , dont
> tweak the environment at all.

If you want to optimize memory, you can configure process pooling. This
means that the .NET runtime, is not loaded several tines, including just a
tiny aspx page which does no important things ( I assume).
Process pooling is done in IIS. Just configure the websites to use the same
process pool.

If I were you, I would run the .NET app in 64 bit mode b.t.w. but that's
another discussion.