About w3wp Memory Usage and Any Benefits to Stripping Application Extensions in IIS6?

How Many Virtual Servers Should Be Associated with a Single Application Pool?

SharePoint Cafe — Fri, 05 May 2006 08:05:01 GMT

re: About w3wp Memory Usage and Any Benefits to Stripping Application Extensions in IIS6?

Paul — Sat, 09 Jun 2007 07:27:36 GMT

50 Megs is nothing!!! I am running WS2003 and IIS6.0 and one site is hitting 180 - 200 Megs on the w3wp.exe I am on a VPS plan that gives me 384 Megs Memory, and I am hitting ceiling about 100 times a day, causing out of memory exceptions. One thing I would recommend is always seperate your websites into seperate App Pools, especially if you have a Web based Stats and Email ( Smartermail and smarterstats ) I have set the App pools for those applications to shutdown after 2 minutes of inactivity, this has helped to free up alot of memory for my website. My Host is telling me I have to upgrade to their 1/2 gig memory VPS plan to solve the problems, and I am trying to figure out ways get around this costly upgrade. Does anyone know of another way to Jew down your memory usage. Or at least prevent your VPS from hitting ceiling? And No I am not hosting the DB on the same box,

re: About w3wp Memory Usage and Any Benefits to Stripping Application Extensions in IIS6?

David.Wang — Sun, 24 Jun 2007 09:46:00 GMT

Paul - you have already exhausted all your choices.

You either have to:

1. run applications that use less memory

2. be more aggressive with idle-timeout to remove unused applications from memory

3. run in an environment with more memory

If you look through computer software history, you may notice another choice - some people tried to compress their applications in memory and uncompress it at runtime (i.e. trade CPU cycles for RAM). However, that approach flopped when RAM prices dropped every 6 months.

//David

re: About w3wp Memory Usage and Any Benefits to Stripping Application Extensions in IIS6?

Pritesh — Sun, 29 Jul 2007 13:55:24 GMT

In My Web server only one Web services Running there is no isolation required then also w3wp.exe will take 50 - 80 % CPU usages but not all time week one or tow day. How to handle this IIS behavior??

re: About w3wp Memory Usage and Any Benefits to Stripping Application Extensions in IIS6?

Damian Stals — Tue, 22 Jan 2008 13:18:46 GMT

On our webservers we hover at about 1.8GB of memory for our primary application. We host a CMS solution for about 300 clients. Each client has their own dedicated website running on our box. Our server has 4GB of memory and is running the /3GB switch. However I cannot get IIS to allocate more then 1.8GB. How can I give our main app more memory? Also what about configuring private and virtual byte usage?

Damian

re: About w3wp Memory Usage and Any Benefits to Stripping Application Extensions in IIS6?

David.Wang — Sun, 27 Jan 2008 09:41:49 GMT

Damian Stals - run pure 64 bit applications on 64bit Windows.

IIS does not limit memory allocation in any way, so your 1.8GB limit is coming from your web application. It has health monitoring metrics for private and virtual byte allocation, but that does not *limit* them.

FYI: 4GB RAM and /3GB does not mean a web application will automatically use more than ~2GB memory. /3GB makes 3GB of virtual memory ADDRESS space available to a 32bit process. 4GB physical RAM is purely available to back virtual memory addressing. None of them automatically mean a web application will use more than 1.8GB memory.

Pure 64bit applications use all that available memory by default. You have to do extra work with 32bit applications to access all that memory. Have you done that work?

//David