I have a multi-portal installation of DNN and to avoid the application boot up, I put a web keep alive on one of the portals (from Iowa Computer Gurus). And it works great for that portal. But I assumed that this work work for the other portals as well on that same DNN installation...the thought being that there is just one app pool for the whole instance and so if it is fired up for one portal, it is fired up for all portals...

In actuality, this does not seem to be the case. The portal I have the keep alive on is super fast, no matter when I pull it up. However the other portals are very slow to pull up. Can someone explain this too me?

Thanks in advance, 
Chad

So what I determined is that you do need a keep alive for every Application Pool, which may or may not be synonymous with a portal...it depends on your application set up. My hosting provider has you set up each top level domain as a website....then at the website level, it creates a new Application Pool for it to run in...even though the website then points to the same instance of DNN as multiple other websites...but each website has its own app pool and hence requires a keep alive.