Web Application Stress ( WAS ) tool, simulates multiple HTTP clients making requests to your Web site, while ASP.NET includes a number of performance counters that you can use to track the execution of your application.
create a custom base class for the Global.asax file. This base class inherits from the HttpApplication class, just like the default Global class that sits behind the Global.asax file. The custom base class provides the same members as the default Global.asax file, but even better, you can extend the class with additional members, such as custom properties for tracking counters.
This counter measures (in milliseconds) how long it takes for the Web application to service a request. TTLB is a key
indicator of how scalable an application is.
Use as much of Stored Procedure as you can instead of queries inside the application. By this the execution happens at the backend and only results are returned thereby increasing performance and speed.
Yes. It dynamically disables public (or client) caching and switches the page to use server caching. This is because the substitutions need to happen via server-side logic.
It can be implemented in 2 methods:
1. Call the new Response.WriteSubstitution method, passing it a reference to the desired
substitution method callback.
2. Add a control to the page at the desired location, and set its
methodName attribute to the name of the callback method.
The following statement fetches all the objects in cache and stores in a dictionary object.
IDictionaryEnumerator CacheEnum = HttpContext.Current.Cache.GetEnumerator();
1. Easy to implement.
2. Data is cached at client side hence supports Web Farms
3. Most of the browsers support them
4. Reduces usage of server resources