Last post Apr 17, 2013 10:24 AM by Perkinsville
Apr 16, 2013 03:42 PM|sugarcrum|LINK
Have a fairly large site trying to solve for first time hit penalties. Attempting to use aspnet_compiler to pre-compile does not seem to be working as I thought it would.
I run the command as follows:
aspnet_compiler -p "C:\Development\Source\WEB" -v / "C:\Staging" -c
Web.Config setting as follows (not sure if this matters?)
<compilation debug="false" strict="false" batch="true" explicit="true" targetFramework="4.0" optimizeCompilations="true">
IIS app pool (values can't be changed due to third party references)
Running Windows Server 2008R2
When I navigate to the first page (login) in the site (C:\Staging) I get appx. 60 second warm-up in which I can see the files caching/compiling in the temp directory
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files.
My assumption was that by using the aspnet_compiler I would be able to bypass the need for this warm-up cycle. Is there something obvious I'm missing or some other means of pre-compiling such that
we don't have this first time penalty?
This seems to happen (no real proof) through the day, possible when the app pool recycles? Again, looking for some way to solve.
Thanks for any help
Apr 17, 2013 10:24 AM|Perkinsville|LINK
You might want to look at application initialization.
Once configured the worker process will be automataclly started and a dummy request sent to the web site so the page(s) is compiled.
I also wrote this article which might help get this implemented.
It is supported on IIS 7.5 too, you just need to download the module and install it, recommended using the Web Platform Installer.