【正文】 r process ? Connectionbased routing w/in Garden ? Not processor based (can enable on 1 CPU server) ? Processor Affinitization ? Bind app pool process/es to 1 or more CPUs ? Maskbased configuration Worker process ISAPI Extension ISAPI filter Worker process ISAPI filter Web Garden application pool W3SVC Scalability Best Practices IIS 6 Web Gardens and Processor Affinity Scalability Best Practices Web Gardens and Processor Affinity BPs ? Web Garden Best Practices ? Not beneficial in most cases – only good for following specialized applications: ? Application is multiinstanceable ? Application is not CPUintensive ? Application has synchronous high latency backend (or sync high latency anywhere) ? Affinity Best Practices ? Affinitize pool to a POD (or hemisphere) ? In general, 4CPU is optimal case for affinity ? Try affinitizing NICs to CPUs too (distribute NIC interrupts) ? Done using SMPAffinitized = True amp。 P Manager WMI Manager IIS TCP/IP kernel user WinSock INETINFO Metabase WAS Worker Process Web Service Applications (ISAPIs) W3 Core DLL Worker Process Applications (ISAPIs) W3 Core DLL Web Garden ISAPI Exts amp。 however, it has other duties, such as: ? Managing TCP connections. ? Validating HTTP requests ? Routing HTTP requests to the correct application pool. ? Caching of responses in kernel mode. ? Performing all textbased and centralized binary logging for the Web service (not ODBC). ? Implementing features such as connection limits, connection timeouts, queuelength limits, and bandwidth throttling for IIS. Https Cache Flow IIS New Isolation Mode ? 應用程序隔離的目的 ? IIS ? IIS ? Worker process isolation mode ? IIS isolation mode IIS IIS isolation mode Worker process isolation mode Worker Processes and App Pools ? Application Pool workhorse ? Handles requests routed to app pool ? Miniweb servers ? Contains all W3SVC functionality ? Loads ISAPI’s – both site filters and extensions ? Separates W3SVC from INETINFO Web Admin Service Universal Listener Worker Process Worker Process Worker Process Worker Process W3ADM’s Management Role ? W3ADM is responsible for controlling the lifetime of the worker processes: ? When to start a worker process ? When to recycle a worker process if it is unable to process any more requests (bees blocked). ? CPU monitoring is configured to stop an app pool after consuming too much CPU. ? Initiation of rapidfail protection causes an application pool to stop. ? A configuration error caused by trying to use an incorrect identity causes an application pool to stop. ? A Windows administrator performs a demand stop or start on an application pool. ? In IIS5IM mode, W3ADM will try attempt to restart INETINFO if it crashes. Worker Process ? Contains a master DLL () that implements all request handling logic ? Requests are routed through to the worker process and W3SVC ? Is effectively administered and managed by W3SVC ? Can be loaded into INETINFO (IIS5IM) or (WPIM) ? Serves only one app pool Application Pools ? A group of one or more URL namespaces served by a worker process ? Can be started and stopped like sites ? Can be configured for health detection, recycling, etc.