How to go about reducing ASP.NET MVC application startup Memory Footprint?

I have an ASP.NET MVC application that also employs the typical NHibernate / Castle stack. On startup, the application's memory footprint sits around 190Mb and I wish to be able to run multiple isolated AppPools, each of which will serve a different domain. This is before really hitting anything serious in the database or putting anything in the ASP.NET Cache.

How would you go about reducing the standing footprint of the app?

I've looked at this article here on CodeProject which talks about sharing common DLLs in a specific AppDomain. Does 开发者_开发问答anyone have any experience using this technique on ASP.NET?

One simple way would be to use a shared web service (WCF) that will perform the data access so that each application wouldn't bother with it.