helldanger1
GForum VIP
- Entrou
- Ago 1, 2007
- Mensagens
- 29,631
- Gostos Recebidos
- 1
Overview
The FastCGI Extension for IIS 6.0 enables popular application frameworks that support FastCGI protocol to be hosted on the IIS web server in a high-performance and reliable way. FastCGI provides a high-performance alternative to the Common Gateway Interface (CGI), a standard way of interfacing external applications with Web servers that has been supported as part of the IIS feature-set since the very first release.
CGI programs are executables launched by the web server for each request in order to process the request and generate dynamic responses that are sent back to the client. Because many of these frameworks do not support multi-threaded execution, CGI enables them to execute reliably on IIS by executing exactly one request per process. Unfortunately, it provides poor performance due to the high cost of starting and shutting down a process for each request.
FastCGI addresses the performance issues inherent to CGI by providing a mechanism to reuse a single process over and over again for many requests. Additionally, FastCGI maintains compatibility with non-thread-safe libraries by providing a pool of reusable processes and ensuring that each process will only handle one request at a time.
For additional support information, go to Microsoft Help and Support.
Features
The Microsoft FastCGI Extension for IIS provides full support for hosting and executing FastCGI enabled applications on IIS in high performance and reliable way.
Some of the important features provided in this release of FastCGI Extension are listed below:
Reliable hosting of non thread-safe applications (such as PHP) in FastCGI mode by enforcing single request concurrency per FastCGI process
Support for hosting of FastCGI application frameworks on shared servers by providing necessary configurability.
Rich set of configuration options for tweaking performance of FastCGI extension and FastCGI processes.
The following list describes the most important changes since the Go Live release:
Changes to fcgiext.ini take effect without restarting web service process
When any configuration change is made to fcgiext.ini file the change is picked up by the FastCGI Extension right away, without any need to restart the Web Server process. Because of that it is recommended to use the configuration script (fcgiconfig.js) included in this release instead of the one provided with Go Live release. The configuration script that was included with Go Live release recycled the application pool or restarted the web service every time a configuration change was made. It is not necessary to perform these operations anymore, so the application pool recycling functionality has been removed from the configuration script.
RapidFailsPerMinute configuration setting can be used to control Rapid Failure Protection mode
By default the FastCGI extension goes into Rapid Failure Protection mode, if it encounters more than 10 failures per minute in the FastCGI process pool. The RapidFailsPerMinute setting can be used to specify the number of failures per minute that would trigger Rapid Failure Protection mode.
Configuration script (fcgiconfig.js) can re-create IIS script mappings from fcgiext.ini file
The new command “-syncini” has been added to fcgiconfig.js to allow for re-creation of IIS script mappings by using FastCGI process pool configuration information available in the fcgiext.ini file. For example this command can be used in situations when the FastCGI extension is un-installed and then re-installed, since all script mappings are removed during un-install.
The following bugs have been fixed since Go Live release:
Responses with empty header values caused the FastCGI extension to fail response processing
The status codes logged by the FastCGI extension may be different from what was sent to the client
On 64 bit machines with Enable32BitAppOnWin64 set, fcgiext.dll would look for configuration in \windows\syswow64\inetsrv instead of \windows\system32\inetsrv
Stability under heavy load has been improved
Benefits
Most applications built to for IIS take advantage of the native, multi-threaded extensibility model of IIS. Many popular applications, particularly those written or originally designed for Linux, are not multi-threaded, and instead take a multi-process approach to concurrency. While the PHP engine itself is multi-thread capable, many of the popular PHP extensions are not, requiring a single concurrent request guarantee to operate reliably. This forces the use of CGI and results in poor performance on the Windows platform. FastCGI helps these application frameworks to achieve improved performance on Windows over CGI, while allowing stable operation in production environments.
Requirements
To use FastCGI extension, you must have one of the following operating systems with IIS installed:
Windows Server 2003 SP2 (IIS 6.0)
Windows Server 2003 x64 edition (IIS6.0)
Download
The FastCGI Extension for IIS 6.0 enables popular application frameworks that support FastCGI protocol to be hosted on the IIS web server in a high-performance and reliable way. FastCGI provides a high-performance alternative to the Common Gateway Interface (CGI), a standard way of interfacing external applications with Web servers that has been supported as part of the IIS feature-set since the very first release.
CGI programs are executables launched by the web server for each request in order to process the request and generate dynamic responses that are sent back to the client. Because many of these frameworks do not support multi-threaded execution, CGI enables them to execute reliably on IIS by executing exactly one request per process. Unfortunately, it provides poor performance due to the high cost of starting and shutting down a process for each request.
FastCGI addresses the performance issues inherent to CGI by providing a mechanism to reuse a single process over and over again for many requests. Additionally, FastCGI maintains compatibility with non-thread-safe libraries by providing a pool of reusable processes and ensuring that each process will only handle one request at a time.
For additional support information, go to Microsoft Help and Support.
Features
The Microsoft FastCGI Extension for IIS provides full support for hosting and executing FastCGI enabled applications on IIS in high performance and reliable way.
Some of the important features provided in this release of FastCGI Extension are listed below:
Reliable hosting of non thread-safe applications (such as PHP) in FastCGI mode by enforcing single request concurrency per FastCGI process
Support for hosting of FastCGI application frameworks on shared servers by providing necessary configurability.
Rich set of configuration options for tweaking performance of FastCGI extension and FastCGI processes.
The following list describes the most important changes since the Go Live release:
Changes to fcgiext.ini take effect without restarting web service process
When any configuration change is made to fcgiext.ini file the change is picked up by the FastCGI Extension right away, without any need to restart the Web Server process. Because of that it is recommended to use the configuration script (fcgiconfig.js) included in this release instead of the one provided with Go Live release. The configuration script that was included with Go Live release recycled the application pool or restarted the web service every time a configuration change was made. It is not necessary to perform these operations anymore, so the application pool recycling functionality has been removed from the configuration script.
RapidFailsPerMinute configuration setting can be used to control Rapid Failure Protection mode
By default the FastCGI extension goes into Rapid Failure Protection mode, if it encounters more than 10 failures per minute in the FastCGI process pool. The RapidFailsPerMinute setting can be used to specify the number of failures per minute that would trigger Rapid Failure Protection mode.
Configuration script (fcgiconfig.js) can re-create IIS script mappings from fcgiext.ini file
The new command “-syncini” has been added to fcgiconfig.js to allow for re-creation of IIS script mappings by using FastCGI process pool configuration information available in the fcgiext.ini file. For example this command can be used in situations when the FastCGI extension is un-installed and then re-installed, since all script mappings are removed during un-install.
The following bugs have been fixed since Go Live release:
Responses with empty header values caused the FastCGI extension to fail response processing
The status codes logged by the FastCGI extension may be different from what was sent to the client
On 64 bit machines with Enable32BitAppOnWin64 set, fcgiext.dll would look for configuration in \windows\syswow64\inetsrv instead of \windows\system32\inetsrv
Stability under heavy load has been improved
Benefits
Most applications built to for IIS take advantage of the native, multi-threaded extensibility model of IIS. Many popular applications, particularly those written or originally designed for Linux, are not multi-threaded, and instead take a multi-process approach to concurrency. While the PHP engine itself is multi-thread capable, many of the popular PHP extensions are not, requiring a single concurrent request guarantee to operate reliably. This forces the use of CGI and results in poor performance on the Windows platform. FastCGI helps these application frameworks to achieve improved performance on Windows over CGI, while allowing stable operation in production environments.
Requirements
To use FastCGI extension, you must have one of the following operating systems with IIS installed:
Windows Server 2003 SP2 (IIS 6.0)
Windows Server 2003 x64 edition (IIS6.0)
Download