I Have three instances of DotNetNuke running on the same server.   I've configured each site to use the same application pool named "dotnetnuke".  So when I look at the app pool called DotNetnuke I have three application names(one for each instance of dnn).   When I look at task manager I see just one worker process running as expected.

So the question is, if instance 1 and 2 get an average of 1 visit a day, and instance 3 gets say 1 visitor every 2 minutes, since they are all in the same application pool does this mean that site 1 and 2 will basically be kept alive by the fact that instance 3 gets hit enough to keep from recycling?

Thanks

Josh

Josh Martin

I'd be curious what others have to say because there was a thread recently that had some claims about multiple applications in the same app pool NOT all showing a woken state as expected. I don't recall what the reasoning or premise behind the thinking was, and couldn't find the thread to reference here for you.

Personally, I believe that the answer to your question is yes, but keep in mind that you also have other options. The idle timeout doesn't necessarily have to be checked. And the site(s) can be precompiled as well.

There are of course benefits to splitting your 3 sites to their own respective app pools, but maybe you already know the pros/cons of ebrything I just mentioned.

EDIT- I just saw Cathal's post when submitting this one, and appreciate the fact that he used AFAIK. When I looked into this some time ago with sites on IIS 6, they seemed to exhibit the domain-specific behavior that he describes - all domains in an app pool needed to be pinged for keep alive. But I'm not seeing the same type of behavior in IIS 7.5 - a single keep alive to one domain in the common app pool seems to keep every domain in the pool alive and they snap right into the browser.

Thanks Eric, some great links there. I was vaguely aware of the asp.net 4.0 warmup feature as Scott Guthrie blogged it @ http://weblogs.asp.net/scottgu/archive/2009/09/15/auto-start-asp-net-applications-vs-2010-and-net-4-0-series.aspx , but wasn't aware that you could do that in IIS 7.5 without having .net 4.0 installed - good stuff.

Cathal