In the definition of the management area--virtual host product, you can set the number of people in a pool to share
On a server, the total number of general pools should not exceed 20 from the perspective of performance.
Therefore, the pool becomes a valuable resource.
The fewer the number of people in a pool, the higher the stability and performance of the pool. Therefore, the number of people in a pool should be related to the charges, that is, the higher the charges, the fewer the pools are shared.
Generally, you can consider this way, and charge a virtual hosting product worth 100 yuan, shared by 50 people. 5 people who charge 1,000 yuan will share it.
For shared servers (the total number of websites is less than 30), you can consider that the number of people in the pool is set to 1. In this way, one website is one pool. In the case of one website is one pool, the "recycling pool function" and "setting FSO function" will be automatically added to the host panel, and such users will have stronger control capabilities.
For users who are used as free virtual hosts, the number of users can be set to 20,000 (20,000), which can ensure that all websites are placed in one pool, which can greatly reduce the amount of memory usage.
The general principle is that the more pools, the more memory it will be used, but the more stable a single website is, the fewer pools, the less memory it will be used, but the stability of a single website will be reduced.
If there are already hundreds of websites, it will be troublesome if you want to adjust it. You can use the following tools to reassign the application pool to solve the problem.
IIS program pool batch allocation tool
On a server, the total number of general pools should not exceed 20 from the perspective of performance.
Therefore, the pool becomes a valuable resource.
The fewer the number of people in a pool, the higher the stability and performance of the pool. Therefore, the number of people in a pool should be related to the charges, that is, the higher the charges, the fewer the pools are shared.
Generally, you can consider this way, and charge a virtual hosting product worth 100 yuan, shared by 50 people. 5 people who charge 1,000 yuan will share it.
For shared servers (the total number of websites is less than 30), you can consider that the number of people in the pool is set to 1. In this way, one website is one pool. In the case of one website is one pool, the "recycling pool function" and "setting FSO function" will be automatically added to the host panel, and such users will have stronger control capabilities.
For users who are used as free virtual hosts, the number of users can be set to 20,000 (20,000), which can ensure that all websites are placed in one pool, which can greatly reduce the amount of memory usage.
The general principle is that the more pools, the more memory it will be used, but the more stable a single website is, the fewer pools, the less memory it will be used, but the stability of a single website will be reduced.
If there are already hundreds of websites, it will be troublesome if you want to adjust it. You can use the following tools to reassign the application pool to solve the problem.
IIS program pool batch allocation tool