Article ID: 116021, created on Apr 26, 2013, last review on Jun 5, 2015

  • Applies to:
  • Operations Automation

Resolution


An IIS Shared Hosting server registered in POA has the following capacities defining number of IIS shared application pools which will be created on a host:

  • Number of IIS Shared Application Pools (iis.capacity.shared_app_pools.value)
  • Number of IIS Shared Application Pools for ASP.NET2 (iis.capacity.shared_app_pools_for_asp.net2.value)
  • Number of IIS Shared Application Pools for ASP.NET2 in Integrated mode (iis.capacity.shared_app_pools.integrated.value)
  • Number of IIS Shared Application Pools for ASP.NET4 (iis.capacity.shared_app_pools_for_asp.net4.value)
  • Number of IIS Shared Application Pools for ASP.NET4 in Integrated mode (iis.capacity.shared_app_pools_for_asp.net4.integrated.value)

The default value of all the listed parameters is 5, Provider may change the values of the parameters any time. Total number of shared application pools on an IIS server is the sum of values of all parameters listed above.

The description of the way how exactly POA creates IIS shared application pools on a particular host is provided below.

When a new IIS server is registered in POA it will not have any webspaces on it and POA will not create any shared application pool at the moment of host registration in the system.

The very first shared application pool will be created on an IIS host during provisioning of the first customer's webspace with shared application pool on the host. When provisioning the second webspace (with shared application pool) on the IIS host POA will create the second shared application pool, and so on until capacity for current type of shared application pools is reached. After capacity of some type of IIS shared application pools is reached POA will start reusing created application pools, i.e. POA will start to configure new webspaces to use existing shared application pools.

The same approach is used if Provider increase capacity of any type of shared application pools on an IIS host: when POA will create the very fist customer's webspace (with shared application pool) on the host after capacity was increased the new shared application pool will be created; POA will create new shared application pools until new limit configured in capacity is reached. After the limit is reached POA will start re-using created shared application pools.

The approach described above means that capacity on IIS shared application pools will be reached quite soon after new host is put in production, it is enough to create as many customers' webspaces (with shared application pool) as limit configured in capacity.

After capacity on any kind of IIS shared application pools is reached POA will send corresponding notification to Provider. The notification does not mean any problem with a particular IIS host mentioned in notification, it just means that POA created as many shared application pools as limit configured in the corresponding capacity and it will start re-using created pools for new customers' webspaces. Provider may increase the capacity and after POA create a number on new webspaces Provider again will receive notification about capacity reached limit, again - the notification itself does not mean problem with the IIS server.

caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF