A few pieces of advice:
- Sort your profiles by wall clock time if you want to get something useful from them.
- Class::DBI will hurt you a lot on this test. It's at least 5 times slower than straight DBI code using prepare_cached, bind_columns and bind parameters.
- A straight mod_perl handler would be faster than Catalyst and is more equivalent to a vanilla servlet environment. You'd have to make sure you set the TT part up right though, so don't try this if you aren't familiar with TT's caching.
- DBD::Oracle has a parameter for tuning how many rows to fetch at once. It makes a big difference. Crank it up high.
- Make sure you have MaxClients set at something that prevents your server from using up all the memory and going into swap. That would kill your performance.
Finally, don't feel bad if you don't win. Java is fast these days when used in a lightweight environment like Tomcat.
-
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.
|
