iis60入门及进阶系列之四(编辑修改稿)

iis60入门及进阶系列之四(编辑修改稿)内容摘要：

st Practices Isolating Apps in Application Pools  Can create one or more application pools  Each served by one or more .  Each serves only one pool.  Reqs routed directly to pool by  Isolate applications based on:  Site/Customer  Functionality  Reliability  Application version (as long as each has separate URL)  Best Practices  Timeout Pool: put misbehaving applications in a more restrictive pool  Leaks → throttle back memory usage  Crashes → enable Rapid Fail Protection.  Isolate critical applications in their own pool  best practice – separate ASP and applications  Pinging  Periodic check to ensure at least 1 thread is available to do work  Can set Frequency of Ping, response time per pool  Orphaning if ping fails, can take “action”  REPORT_UNHEALTHY  ISAPI SSF  Used with Ping to request a “recycle” if unhealthy  ASPNET used in conjunction w/ResponseDeadlockInterval  Best Practices  Use Pinging to ensure IIS w3wp and ASPNET have threads available to do work  Check NT174。 App Log for Warnings from W3SVCWP Event Type: Warning Event Source: W3SVCWP Event Category: None Event ID: 2262 Date: 5/4/20xx Time: 1:02:33 PM Computer: COMPUTERNAME Description: ISAPI 39。 C:\39。 reported itself as unhealthy for the following reason: 39。 Deadlock detected39。 . Reliability Best Practices Pinging == Auto Health Detection Reliability Best Practices Periodic Process Recycling  What is it?  Periodically restart applications based on:  [Default] Uptime  of requests  Scheduled time  Memory consumption (virtual memory and actual used memory)  Ondemand  Why use it?  Refresh apps to ensure availability  Prevent bad apps from taking over the system  Session/App State  Inproc state is lost when process is terminated  Use OOP Session State management (ASPNET_STATE, SQL) to persist state! kernel user W3SVC Old Worker Process ASPNET Web Proc. Core DLL Ready for Recycle Request Reliability Best Practices Overlapping Recycle kernel user W3SVC Old Worker Process ASPNET Web Proc. Core DLL Ready for Recycle New Worker Process ASPNET Web Proc. Core DLL Request startup Reliability Best Practices Overlapping Recycle kernel user W3SVC Old Worker Process ASPNET Web Proc. Core DLL New Worker Process ASPNET Web Proc. Core DLL ready Reliability Best Practices Overlapping Recycle kernel user W3SVC Old Worker Process ASPNET Web Proc. Core DLL New Worker Process ASPNET Web Proc. Core DLL Shut down Request Reliability Best Practices Overlapping Recycle kernel user W3SVC New Worker Process ASPNET Web Proc. Core DLL Request Reliability Best Practices Overlapping Recycle Overlapping Recycle  Terminates only old process after new process starts  Possible for apps to be instantiated multiple times NonOverlapping Recycle  Terminates old process first  Then starts new process to replace it  Reduces multiinstance problems BOTH still queue requests in the kernel – No interruption in service! Recycling Overlapping vs. NonOverlapping Reliability Best Practices Recycling Best Practices  Overlapping Remendations  Use Ov。