ASP.NET startup Performance profiling web

Question

I\'m trying to determine the cause of a very long (imho) initial start up of an ASP.NET application.

The application uses various third party libraries, and lots of refe

Answer 1

Entertainment options check along with profiling:

• profile everything, add time tracing to everything and log the information
• if you have many ASPX views that need to be compiled on startup (I think it is default for release configuration) than it will take some time
• references to Web services or other XML serialization related code will need to compile serialization assemblies if none are present yet
• access to remote services (including local SQL) may require the services start up too
• aggressive caching in application/remote services may require per-population of caches

Production:

• What is the goal for start up time? Figure out it first, otherwise you will not be able to reach it.
• What is price you are willing to pay to decrease start up time. Adding 1-10 more servers may be cheaper than spending months of development/test time and delaying the product.
• Consider multiple servers, rolling restarts with warm up calls, web gardens
• If caching of DB objects or in general is an issue consider existing distributed in-memory caches...