A short benchmark (like the one he did) is meaningless, since it has so little resemblance to a real program. A longer one takes more time to do well. Responding to trolls is not worth the days or weeks of effort that it takes to make a legitimate and interesting benchmark.
If you're interested in seeing benchmarks done to demonstrate Perl's performance, you should aim to create something more useful that can be shown to business people in the IT field; something along the lines of the benchmarks they publish for application servers in eWeek or similar publications. Meanwhile, you are welcome to look at this benchmark which puts mod_perl up against Resin and Tomcat. In both tests, mod_perl is faster and uses less memory. Source code is available for you to run it yourself.
-
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.
|
