Shulou(Shulou.com)06/02 Report--

In this issue, the editor will bring you about the reason why mod_python is better than traditional CGI in performance. The article is rich in content and analyzed and described from a professional point of view. I hope you can get something after reading this article.

The specific operation of mod_python in the actual application operation process I personally have been puzzled, said that today we will provide the following articles on the actual operation of mod_python in the difficulties, do a relevant answer, I hope you will gain something.

Performance

One of the main advantages of mod_python is that it surpasses the traditional CGI in performance. Here is a very rough test. The test was done on a Pentium 1.2G machine running Red Hat Linux 7.3g. Ab is used to test four scripts, all of which are input from a standard cgi module (because this is how a typical Python cgi script starts), and then output a simple word "Hello!". This result is based on 10000 requests with a concurrency of 1.

Standard CGI: 23 requests/s Mod_python cgihandler: 385 requests/s Mod_python publisher: 476 requests/s Mod_python handler: 1203 requests/s

Adaptability

Apache processes requests in phases (such as reading requests, parsing header, checking access paths, and so on). These phases can be called functional implementations of "handler". Traditionally, a "processor" is a module written in C and compiled into Apache. Mod_python provides a way to extend Apache functionality through the Apache processor written by Python.

For a detailed description of the Apache request processing process, see Apache API Notes, or

Mod_python-Integrating Python with Apache

To easily migrate from CGI, a standard mod_python processor provides a simulated CGI environment that allows users to run legacy scripts under mod_python (in most cases) without making any changes to the code.

See Also:

Apache Developer Resources

Mod_Python-Integrating Python

With Apache, presented at Python 10

Mod_python originated from a project called Httpdapy (1997). For a long time, Httpdapy has not been called mod_python because Httpdapy is not specific to Apache. Httpdapy was designed to be cross-platform and was actually originally written for Netscape server (then known as Nsapy) (1997)

This summary of Httpdapy's README file is a good illustration of the challenges and solutions of embedding Python in HTTP server. The above article is an introduction to the practical application of mod_python.

These are the reasons why the mod_python shared by the editor is better than the traditional CGI in performance. If you happen to have similar doubts, you might as well refer to the above analysis to understand. If you want to know more about it, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.