Maximum Resource Pool size before performance issues
I've heard that you don't want all resouces in a single resouce pool because it will cause a performance issue. Does anyone know the maximum number of users you should have in a resource pool to ensure that you don't have a performance hit?
Re: Maximum Resource Pool size before performance issues
Right now, we are using the recommended setting of 250 from the SysAdm Guide:
Determines the maximum number of resources in a resource pool. If the number of resources exceeds this value, some features are unavailable on the Resource Pool overview page. The View Resource Load button is not available if the number of resources in that resource pool (or its hierarchy if the â Include children resource pools when calculating load for this resource poolâ flag is selected) exceeds the value set for this parameter. The View Forecasted Demand and Manage Pool Capacity button are also unavailable if the number of resources in the resource pool exceeds the default. However, you can still use the Resource page Manage Participation feature to add or remove resources. Values greater than the default (250) may increase response times and memory footprint when the above operations are performed.