I've noticed as my website gets bigger and bigger, the time my laptop takes to display my page is much longer then say a new projects with minimal references.
I think there are two variables at play that affect ASP.NET warm-up time:
- The quantity of external references
- The time it takes for a worker process to
new()
up each instance per worker process - Additional time for the WCF objects as the ServiceHost may be in an external DLL
First, are those the correct variables to take into account when considering ASP.NET startup time?
Next, it appears that web.config may dispatch other objects for use with certain filetypes (*.svc, *.aspx, Windows Identity Foundation (WIF), etc. ). This too may cause delays in ASP.NET.
Last, my project is created as a "web project" not a "web site". Not sure if this has an impact.
Is my theory full of holes, or is there something I can do to make development on a old laptop any better?