Just for the record:
Today I repeated my benchmark, adding another competitor,
a "real" PerlHandler script. (I simply took the 'clean'
Apache::Registry script and wrapped it inside a proper
Apache handler() sub.) These are the results:
|
Requests per second |
Perl script under Apache::Registry
(using CGI.pm) |
30 |
PHP script |
55 |
Apache::Registry script,
without CGI.pm |
62 |
Apache handler |
69 |
So if you want real performance and you ask me, the answer is
clear: take mod_perl and use what it already has (and it
really has a lot).
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|