3 ms·
From my experience, much of an ASP.NET web app's start time is not so much the JIT-ing but before that, when the ASP.NET runtime compiles pages/views (aspx/csht
by duncans 13y ago
From my experience, much of an ASP.NET web app's start time is not so much the JIT-ing but before that, when the ASP.NET runtime compiles pages/views (aspx/cshtml etc) into *.cs then DLLs. Pre-compiling can mitigate this.
Larger EF models can have quite an impact.
Also if you use New Relic, it can seriously affect startup time too.
- bananas 13y agoYes and no. We ship our views as content as we have a custom UI front end that isn't razor or asp.net. The startup time for us is compiling NH proxies and the fact that our bin dir is huge: http://imgur.com/EyjR5WH http://imgur.com/EyjR5WH It takes forever for the JIT to actually compile all code paths in these assemblies. There's no PDBs in there either. Our domain and NH maps consume 42Mb of that to give you an idea.