Having some informations about current ASP.NET application

[Ravi Ambros Wallau]

Hi:
I would like to have some informations about my current ASP.NET
application:

1. Have access to all instances of HttpSessionState that belongs to my
application; Not only name or GUID, but the instance itself;
2. Have an idea of how memory my application and each session is consuming.
Can this be realized without serialization?
3. Is it effective to perform a cycle of garbage collection from times to
times in my ASP.NET application, or it's just and an extra effort that does
not makes any differences in memory consumption (while there's available
memory)?

Thanks,

--
Ravi
rwallau@_RemoveThisTextAndUnderscore...wirele ss.net

[Jim Cheshire]

On Mon, 16 Jan 2006 17:29:00 -0200, "Ravi Ambros Wallau"
<no****@nospam.com> wrote:

Hi:
I would like to have some informations about my current ASP.NET
application:

1. Have access to all instances of HttpSessionState that belongs to my
application; Not only name or GUID, but the instance itself;
2. Have an idea of how memory my application and each session is consuming.
Can this be realized without serialization?
3. Is it effective to perform a cycle of garbage collection from times to
times in my ASP.NET application, or it's just and an extra effort that does
not makes any differences in memory consumption (while there's available
memory)?

Hi Ravi,

You can do number 1 and 2 pretty easily with Windbg and the SOS
extension.

Regarding number 3, this is a bad idea to do indiscriminately. If you
are freeing a lot of large data structures and are under memory
pressure, calling GC.Collect is not a bad thing. However, it's not
effective to do so "from time to time."
Jim Cheshire
--
Blog:
http://blogs.msdn.com/jamesche

[Ravi Ambros Wallau]

Thanks...
I'll try to find some docs about how to use WinDBG with SOS. SOS is an
extension for the debugger, I guess... Is it possible to access it from my
ASP.NET application? Not recomendable in a production environment, I
guess...
I'm using the Microsoft UIPAB, and I'll execute the GC.Collect()
everytime a new task is started (and the old is purged by other routine that
is executed)...
Is time-to-time a valid expression in English? (I'm Brazillian)... From
time-to-time...

"Jim Cheshire" <no****@nomail.com> wrote in message
news:qc********************************@4ax.com...

On Mon, 16 Jan 2006 17:29:00 -0200, "Ravi Ambros Wallau"
<no****@nospam.com> wrote:

Hi:
I would like to have some informations about my current ASP.NET
application:

1. Have access to all instances of HttpSessionState that belongs to my
application; Not only name or GUID, but the instance itself;
2. Have an idea of how memory my application and each session is
consuming.
Can this be realized without serialization?
3. Is it effective to perform a cycle of garbage collection from times to
times in my ASP.NET application, or it's just and an extra effort that
does
not makes any differences in memory consumption (while there's available
memory)?

Hi Ravi,

You can do number 1 and 2 pretty easily with Windbg and the SOS
extension.

Regarding number 3, this is a bad idea to do indiscriminately. If you
are freeing a lot of large data structures and are under memory
pressure, calling GC.Collect is not a bad thing. However, it's not
effective to do so "from time to time."
Jim Cheshire
--
Blog:
http://blogs.msdn.com/jamesche

[Jim Cheshire]

On Mon, 16 Jan 2006 18:45:47 -0200, "Ravi Ambros Wallau"
<no****@nospam.com> wrote:

Thanks...
I'll try to find some docs about how to use WinDBG with SOS. SOS is an
extension for the debugger, I guess... Is it possible to access it from my
ASP.NET application? Not recomendable in a production environment, I
guess...
I'm using the Microsoft UIPAB, and I'll execute the GC.Collect()
everytime a new task is started (and the old is purged by other routine that
is executed)...
Is time-to-time a valid expression in English? (I'm Brazillian)... From
time-to-time...

Hi Ravi,

I have some documentation on using Windbg and SOS in my blog. It
should help.

There are two ways that you can use Windbg; live debugging and
post-mortem. In a production environment, live debugging is a really
bad idea because no one will be able to use your app while you're
broken into the process. In such a case, getting a hang dump and doing
post-mortem debugging is a much better choice.

Yes, time-to-time is a valid expression in English. :)

Jim Cheshire
--
Blog:
http://blogs.msdn.com/jamesche