Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I recently rented some shared space on (Basic package). I deployed a single ASP MVC3 application that uses NHibernate. It is a very lean app and I have profiled it for memory leaks and on my local IIS 6.1 I never have a problem with it.

However, when deployed to WinHost, the app pool keeps recycling. Their Support say that the Basic package gives you a max app pool size of 100M. I have the same app code running on their Max package and Support tell me that it uses 130MB of its 200MB limit.

Before I run off and upgrade my Basic package to Max, does anyone know if that is a typical size for a lightweight ASP MVC app. It doesn't use session or cache and has very thin pages. It just seems odd to me that you cannot run a single ASP application on their basic package. Are they only designed for static sites or something?

share|improve this question
What is the memory usage on IIS6? – Greg Askew Feb 22 '12 at 2:38
w3wp.exe process starts at 45MB working set size with a basic MVC2 site running. I then kick off my app and it grows to 87MB and stays there, but that is with just one user. – Rob Kent Feb 22 '12 at 8:39
up vote 1 down vote accepted

It's extremely difficult to predict. I've seen lightweight MVC apps with single worker processes consuming 12-1300 MB of memory (yes, 1.3 GB).

As you probably know, the .NET CLR is built around a 2-stage compilation model, meaning that your pre-compiled assemblies still need to be translated from MSIL (Microsoft's implementation of the Common Intermediate Language) into machine code. When a request is first made to an IIS application, all pages are parsed and compiled, and the results are cached in the process' memory.

So your actual output may not be that "heavy", but the process still need to allocate memory for the compiled assemblies and all dependent assemblies loaded from the global assembly cache.

Furthermore, it depends on much more than just the application itself. There's a great deal of difference in the memory an application consumes when it has a request queue of 10 compared to a 1000 hits (even though each request has a low memory footprint).

To me, a 100MB limit sounds like quite a restraint

share|improve this answer
Thanks. I've never really considered it before because my apps have run on corporate servers with lots of resources but shared hosting with 100MB limits is obviously not going to work for me. – Rob Kent Feb 22 '12 at 8:27

Are both yours and the vendor's platform the same bitness? I have found that when running an application on x64, the memory usage increases when compared to x86, and if there are a lot of objects, it can double.

share|improve this answer
I would imagine that they are x64; I am x86. So that could also be a factor. Apparently ASP.NET (CLR) is itself about 60MB on its own. – Rob Kent Feb 22 '12 at 17:17

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.