So I have been tuning the crap out of IIS since 5.1 (believe me that was work).
I have always ran into issues with web services taking a few seconds to minutes warming up.
Warming up is defined by just that site has to load memory and profile identity. Calls are made and it seems like forever to get a status page.
So in my lengthy investigation into getting IIS to do a warmup auto-magically.
I have tuned every dang thing I can.
<site name=”MySite” id=”1″>
<application path=”/” serviceAutoStartEnabled=”true” serviceAutoStartProvider=”PreWarmMyCache” />
<add name=”PreWarmMyCache” type=”PreWarmCache, MyAssembly” /></serviceAutoStartProviders>
<applicationPools><add name=”MyAppWorkerProcess” managedRuntimeVersion=”v4.0″startMode=”AlwaysRunning” />
This enables both admins and Developers to warm-up the web apps/services.
Credit to ScottGu
Don’t forget the next fun thing…
The Machine.config is located in the .net framework. So it can be very touchy. You’ve been warned.
And finally a warm script if your afraid of heavy tweaking…
'Section for writing into a text file
Const FORAPPENDING = 8
strFileName = "C:\Utils\service_status.txt"
Set objFS = CreateObject("Scripting.FileSystemObject")
Set objTS = objFS.OpenTextFile(strFileName,FORAPPENDING)
‘strUserID = Inputbox(“Enter your UserID : . . .”,strUSERID, “AMDopp”)
‘strPassword = Inputbox(“Enter your password : . . .”,strPassword, “”)
On Error Resume Next
Set objHTTP = CreateObject(“Microsoft.XMLHTTP”)
If Err.Number=0 And objHTTP.Status=200 Then
Hget=url & “Has been warmed up successfully at : ” & Now()
wscript.echo ” Has been warmed up : “, hget=url
Hget=url & “Found error at : ” & Now()
wscript.echo “Found Error at : “, hget=url
Set objHTTP = Nothing
copy paste name it <something>.vbs
Go forth and make the internets faster at least IIS websites.