It doesn't really look to me that this benchmark has any practical value, IMO it doesn't benchmark things that does matter, and it doesn't even correctly benchmark the rest. Usually web applications do more than just returning {"message" : "Hello, World!"}, and this "more" generally takes more time than web framework itself. Also, I see that in DB benchmarks some cases use mysql while others use mongodb, how is that web framework benchmark? Ok for college project, but for company it doesn't look professional.
Motivation is also questionable:
Application performance can be directly mapped to hosting dollars, and for a start-up company in its infancy, hosting costs can be a pain point.
What about developers time? One saved man-day may easily pay for server-month. I went recently to China for a week, and wanted to still be able to access twitter. It took me less than three hours to write web based twitter client with Mojolicioius and Net::Twitter, it does something for real, and it is smaller (122 lines, including templates) than HelloServerHandler.java which just sends "Hello, world". Check Mojolicioius::Lite if you want example how to do this with Mojolicious.
-
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.
|
