For those of you who are familiar with my SharePoint Warmup Job utility from SharePoint 2007, this is the new version rewritten for SharePoint 2010 that fixes some bugs & adds a few new features.
Those of us who present, demo or teach SharePoint 2010 have something in common. SharePoint is like any other ASP.NET application in that the first time you hit a page it has to JIT compile the page. Once that's done, subsequent page hits are nice and quick as the JIT compiled page is cached. That is until the IIS application pool is recycled, something those of us SharePoint developers do a lot. The other challenge is that when we present, demo or teach, we might not be in one site for a while, but we want it to "stay alive" like people are using it.
I've created a utility that at scheduled intervals will issue an HTTP/HTTPS request to a specified site collection's homepage, key galleries and key admin pages. This way while presenting, demoing or teaching, you can ensure that the most common pages in your sites are being warmed up and kept alive so when you go to do your demo it's nice and quick.
The installation process is pretty painless: run the batch file that will run the PowerShell file that adds and deploys the solution package. This will deploy an auto-activating Feature that adds a new link to Central Administration's Application Management page:
This page will allow you to select a Web application and then specify which site collections you want to keep warmed up and alive. You can optionally pick which popular pages you want the job to hit and the frequency they are hit.
There's even a special case for Central Administration as different options are shown:
Two Important Notes:
- I've tested this in both the public SharePoint 2010 beta as well as the not so public Release Candidate. So far everything works as expected.
- My target audience includes developers and those who present, demo or teach SharePoint. I don't think this is a "production" utility. Frankly, if you have trouble with your sites warming up, you have to ask yourself why you have no traffic. :)
Got any feedback on more features? Leave a comment on this post.
[Update June 7, 2010] Updated to include extra logging in the SharePoint ULS and event log and fixed a few bugs. Details here.