We have recently migrated to a new web server running Windows Server 2008 R2 and IIS7 and 8GB RAM. We host 50 or so DotNetNuke (ASPX) web sites on this new server and want to know what is the Application Pool best practice. Is it best to put all web sites in the same App Pool (ASP.NET v4.0 Integrated) to limit memory consumption, or split the web sites into groups, with each group using a different Application Pool. Put application protection aside, I am mainly interested in performance benefits, and initial application load time afer inactivity.
We use a Keep Alive windows service which polls each web site every 5 minutes, but we are still getting long average page load times after inactivity. We want to have page loads after inactivity to be as quick as possible.