Skip to main content

Essentials Application Pool Memory

Permanently deleted user

I'd appreciate some input from other Essentials users for comparison purposes - how much memory does your Essentials Application Pool (w3wp.exe process running under Essentials user name) consume?

My Essentials app pool consistently rises above 1,000,000 K in a short amount of time after being recycled. I'd like to know if this is consistent with what other users are experiencing.

Thank you for your input!

0

Comments

5 comments

Date Votes
  • Permanently deleted user

    Are you running any adf sites having the timeout setting too high will cause the worker process to hang on to memory until a site is closed. To get a better answer you might want to let people know how many sites you are running and what server platform you are using, version of essentials, and how many sites you have.

    0
  • Permanently deleted user

    Thanks James, that is a great response. Nick, the more sites you have published and in use, the more the worker process will consume. As well, make sure you have only one instance using that application pool. Are you experiencing any problems with your sites, given the memory usage? If so, what are they? If you are just concerned about the memory usage I would say don't be. The IIS environment tries to capture and cache as much as it can to work efficiently for requests. Given memory is faster than HDD, you will see high memory usage from server/enterprise applications, not just Geocortex.

    Thanks,

     

    Shawn
    0
  • Permanently deleted user

    Sorry - I thought I was subscribed to this thread, or I would have responded sooner. I was more curious than experiencing problems.  I suppose I was just after what was "normal" so that I had a benchmark to go off of.  I didn't remember older versions consuming so much memory, so I wanted to make sure that what I am experiencing is simply normal operation.

    A little more information:

    Windows Server 2008 x64, IIS7, Essentials 3.11.1, 8 sites (none are ADF)

    0
  • Permanently deleted user

    I think it really varies during low activity periods the essentials worker process consumes 300 to 500mb during high activity it can easily go above 1gb. I believe I have seen it go as high as 1.5gb but that is the most I have seen it at. It also depends if users are doing tasks such as printing which seems to increase the memory amount from what I have seen. I have about 15 sites and some are used more than others and I am running the same OS and essentials version that you are using.

    0
  • Permanently deleted user

    These numbers seem normal to me and are quite in line with what you should expect when serving large amounts of geographic data.

    Since it depends entirely on what you are serving, and what you are doing with the data when you get it, there isn't any real 'baseline' to go by, but we do recommend at least 4GB of RAM on a production Essentials Server. If installing Essentials alongside ArcGIS Server you'd probably be best advised to have more, as the 10.1 release of ArcGIS Server will happily use the 4GB of RAM just for itself, and being a Java app now it does not share as nicely with other .NET apps (such as ours) as it used to.

    Also, as Shawn mentions above, at least some of this 'high' memory usage is probably due to the fact that a modern Windows machine will attempt to assign all of the memory you have installed to the various running applications. This does not mean that there is an issue with memory usage, as much of this 'assigned' memory will be relinquished immediately if actually needed by another running process. Provided you are not experiencing slow downs or errors caused by lack of memory it is actually the sign of a healthy Windows system if almost all of the installed memory appears to be continuously in use.

     

     

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post