« Previous Next »

• 10-17-2008, 10:58 AM

  Kanien Joined on 01-31-2008, 12:14 AM Posts 104

  Setting virtual memory limit for recycling Reply Contact  I have many application pools with applications running on one server.  These application pools were consuming 500MB each of virtual memory and I thought that seemed high so I set the recycle virtual memory limit to 200MB.  Now many of the apps are recycling when they reach this limit and as I know existing requests and session details are lost upon recycling.  However I'm concerned that this might not have been the best solution.  Is it normal for an application to use that much virtual memory?  Is there anything else I should be concerned with in regards to setting recycle setting?

• 10-17-2008, 12:36 PM

  In reply to

  Paul Lynch Joined on 05-24-2006, 9:41 AM UK Posts 1,247

  Re: Setting virtual memory limit for recycling Reply Contact Hi, Good question. Unfortunately the answer to the question 'How much memory should an application pool use ?' is 'As much memory as it needs' By way of example, today I was looking at an IIS application pool on a 64-bit Windows 2003 server running SQL 2005 Reporting Services and it was using 4.3GB (yes that is Gigabytes) of memory. So, clearly, if I had imposed an arbitrary limit of, say 2GB, for my application pools then this application would have hit that limit and recycled itself. If your application really does require 500MB of memory then imposing a lower limit is clearly going to cause you some problems. One possible approach to this problem might be to remove all memory limts on your application pools and schedule nightly recycles where possible. You might also want to consider moving to a 64-bit platform if you find that you are reaching the limits of 32-bit Windows. Regards,      Paul Lynch | www.iisadmin.co.uk

• 10-17-2008, 12:42 PM

  In reply to

  steve schofield Joined on 06-10-2002, 8:54 PM MI Posts 3,956

  Re: Setting virtual memory limit for recycling Reply Contact To add to what Paul put.  If possible, I would bring this up to your developers of the application.  If they are doing some aggressive caching or putting stuff into Session objects, it could create a bigger app pool memory footprint.  Paul mentioned great recommendations, the only other angle is "if the app gets too big", put it on a separate server.  Which is a whole other topic.  Steve Schofield Windows Server MVP - IIS http://weblogs.asp.net/steveschofield http://www.IISLogs.com Log archival solution Install, Configure, Forget

• 10-17-2008, 1:20 PM

  In reply to

  Kanien Joined on 01-31-2008, 12:14 AM Posts 104	Re: Setting virtual memory limit for recycling Reply Contact  These applications are hosted on a shared hosting server, thus I cannot allow them to use as much as they need.  They are playing in the same sandbox and need to be respectful of the other applications use of server resources.  I'm not confident on what a standard setting should be for a virtual memory limit.

• 10-21-2008, 3:56 PM

  In reply to

  anilr Joined on 05-23-2006, 10:13 PM Redmond, WA Posts 2,343

  Re: Setting virtual memory limit for recycling Reply Contact Unlike private bytes/committed bytes, how much virtual memory one process uses has no impact on how much virtual memory is available to another process.  Virtual memory is really not a good indicator of health of a process on x64 anyway since processes will typically reserve large amount of virtual memory which they will never use. Using private bytes limit for recycling would make much more sense. Anil Ruia Senior Software Design Engineer IIS Core Server