Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I understand that the JIT code is machine specific. Is it possible to create JIT code on the published machine and have IIS use that (instead of the dlls)? The reason I am asking is that every time the app pool restarts, there is a delay in the loading of the application. This delay is due to the fact that the JIT compiled code is getting loaded up into the worker process.
ASP.NET is great, except for the loooooooooong application initialisation times – however said times are not just about JIT compilation, there are other delays that are involved, that unfortunately cannot be worked around. You’ll find that an ASP.NET application that has not a single *.aspx file (such as a raw IHttpHandler) will still have a long init time.
The only solution is a workaround: get a Scheduled Task (a
cronjob in *nix terminology) or a third-party web-polling service that sends an innocuous GET request to your website every so-often. IIS also (had) available a pre-warmer extension, but it’s gone AWOL for some reason.