Default Application pool
==========
Don't touch it. Make sure there is nothing to use it.
Never delete it. Why? Because IIS does not like it. If you delete it, IIS will go crazy.
Do not rename it.
- Performance application pool settings: shutdown 10 minutes after being idle.
- Health Application pool settings: Disable pinging and rapid failure.
Cantral Admin App Pool and SSP Admin App Pool
============
- Reconfiguring Application Pool Settings:
- Recycle at AM to AM every night.
- Maximum physical memory and maximum virtual memory. These App pools do not consume much memory. if the limit is required, I will limit it to 500 MB on a typical system. you can limit them to 200 MB if you want to keep them conservative. they really shouldn't need so much memory.
- Performance Application Pool Settings:
- Shutdown after ten minutes of idle. These App pools do not need to be run all the time, because they are only for management.
- Don't worry about CPU. If you really want to limit it, set it to 5%.
- Do not think about Web Garden. You never really want to expect a w3wp.exe running time too long.
- If you really want to save memory, you should share an app pool between central and ssp. based on security considerations, if you have two teams managing ssp and central, do not share them.
- Health Application Pool Settings:
- Pinging: Disable.
- Rapid failure: uncheck out.
- Startup/Shutdown: You don't want to see errors reported when they are started or stopped because they are a little slow. We recommend that you change the two restrictions to 300.
- Identify Application Pool Settings:
- Use a separate account. If any problem occurs, check the account first.
SharePoint App Pool or % Your Content App Pool % (Whatever you call it)
==============
- Reconfiguring Application Pool Settings:
- Turn Off recycling by minute.
- Recycle at AM to AM every night.
- Maximum physical and virtual memory: This configuration requires a lot of control. this part is used to recycle the Application Pool when too much memory is consumed. in physical memory, when the App Pool data on 32-bit systems is not much, the limit is generally between MB and MB. if there is a total of 2 GB memory, the maximum is MB. 4 GB memory is limited to 1200 MB or up to MB. if the 64-bit front-end has a total of 8 to 16 GB memory, I have heard that the limit is 2 GB, or even not limited.
- Performance Application Pool Settings:
- Idle timeout, disabled. do not enable this option unless the App Pool is not frequently used.
- Request queue. Do not select.
- CPU limit, do not select. These web app pools are exactly where you want to use the cpu.
- Do not use Web Garden.
- Health Application Pool Settings:
- Pinging: Keep enabled. You can ping it every 10-15 minutes to keep it running.
- Rapid failure: do not select this option unless you only have one web application using this app pool and all the content is in this app pool.
- Startup/Shutdown: You don't want to see errors reported when they are started or stopped because they are a little slow. We recommend that you change these two restrictions to 300 to 900.
- Identify Application Pool Settings:
- Use a separate account. If any problem occurs, check the account first.
For web garden, MSDN explains:
Because web garden enables multiple processes, each process has its own copy of application state, in-process session state, caches, and static data. all applications should not use web garden, especially when they need to maintain state. make sure that the performance is measured before determining whether the web garden mode is appropriate.
When using web garden, it is important to understand the running mechanism of session state and round robin. It is also important to understand how other application configurations affect the application.
In my experience, if I use an extra worker process, I can improve the performance of a web application. however, troubleshooting is very difficult, and process isolation is also very difficult. developers do not like it either. before I draw a conclusion that web garden will never be used, Please configure according to the above recommendations. if you want to improve the performance, first test a work process and then test two. if no improvement is made, do not use it.
Translated from:
Recommendations for SharePoint Application Pool Settings
Http://blogs.msdn.com/ B /joelo/archive/2007/10/29/sharepoint-app-pool-settings.aspx
