|
The WebProfiler was created to assist the .Net web developer and the IIS
administrator to analyze memory usage of a web application
during runtime. Apart
from analyzing memory usage, the profiler will also assist in looking at data as
it is stored by an Asp.Net web application.
|
|
|
|
The WebProfiler allows for analysis and profilling of the following
asp.net web components
|
 |
Asp.Net Cache
|
|
|
The cache is used as a persistant data storage mechanism to store static
application data. Data can be managed in terms of usage and expiration.
The cache is managed internally by the runtime and only a little intervention is
needed from the developer |
|
 |
Application State
|
|
|
Application state is memory which is allocated to the application on a global
level and is avalilable to all sessions. The application state is very similiar
to the cache except that data does not expire and will be available for the
entire lifetime of the asp.net web application |
|
 |
Session State
|
|
|
Session state is where we typically store a user's data. A new session state
will be created, each time a connection is made to the server using a web
client. Your web application will execute your code on the server and only
render formated data to the user's browser in the form of html. Using the
session state properly may prove to be a challenge unless we are very carefull,
regarding the information we store. The web profiler helps in analyzing this
data to ensure optimal memory usage, |
|
|
|
|
The profiler will display all content in the asp.net cache and application
state. It will also display all active sessions in the application along with
the content in each session. Sizes of all serializable objects will be
calculated and displayed for drill down into managed object properties and
contents by the developer or administrator. |
|
|
|
|