Recycling settings for ITAM/APM Application Pools in IIS
Article ID: 140917
Updated On:
Products
CA IT Asset Manager
CA IT Asset Manager Asset Portfolio Management
ASSET PORTFOLIO MGMT- SERVER
Issue/Introduction
Are there recommendations for these IIS Application Pool parameters for ITAM/APM
- Request Limit
- Virtual Memory Limit
- Private Memory Limit
Here are the steps to access these parmeters in IIS:
1. Open the IIS Manager
2. Click on the “Application Pools”
3. Highlight an Application Pool and click “Advanced Settings” in the “Action” Pane
4. Scroll down to the “Recycling section”
Environment
Asset Portfolio Management 17.x
All Supported Windows Operating Systems
Resolution
Recycling based on memory limits is not usually necessary in a 64-bit environment, and therefore recycling need not be enabled.
Application pools recycle if the memory limits have been enabled and exceeded. Unnecessary recycling can result in dropped requests from the recycled worker process and slow performance for end-users who are making requests to the new worker process.
The IIS 8.5 default setting for Recycling is after 29 hrs (1740 mins) which will cause the app pool to recycle at that interval, which should be sufficient.
For ITAM in specific, on Application_start after recycle, we load metadata from the database and cache it for the subsequent page requests. An app pool recycle will cause it to reload unnecessarily, which further causes page loading delays to the end-users.
So, we recommend to have default values for private, virtual memory limits (=0) and Request Limit, but have good resources (RAM) on the server.
With the above said, we recommend you to leave the IIS App Pool defaults for ITAM.
Application pools recycle if the memory limits have been enabled and exceeded. Unnecessary recycling can result in dropped requests from the recycled worker process and slow performance for end-users who are making requests to the new worker process.
The IIS 8.5 default setting for Recycling is after 29 hrs (1740 mins) which will cause the app pool to recycle at that interval, which should be sufficient.
For ITAM in specific, on Application_start after recycle, we load metadata from the database and cache it for the subsequent page requests. An app pool recycle will cause it to reload unnecessarily, which further causes page loading delays to the end-users.
So, we recommend to have default values for private, virtual memory limits (=0) and Request Limit, but have good resources (RAM) on the server.
With the above said, we recommend you to leave the IIS App Pool defaults for ITAM.
Feedback
Powered by
