4 ms·

This is great. I hope they make this available for web apps because we've got 45 second warmup time and CPU spamming due to the massive size of the work the JIT

by bananas 13y ago

This is great. I hope they make this available for web apps because we've got 45 second warmup time and CPU spamming due to the massive size of the work the JIT has to do when we deploy. Total pain. I imagine this would help them keep costs down on Azure as well.

kennethh 13y ago
It is possible to precompile web apps already today.
- bananas 13y ago
  I'm talking these two steps, not page precompilation: 1. Proxy generation (castle) -> IL 2. IL -> Native.
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 ago
  Yes 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.