Performance is often misunderstood... most frequently performance issues come from 2 sources... (a) database access, and (b) file system access (like writing logs). What's important to note... neither one of these is related to a particular language. Caching and data pre-preparation go a long way to resolving these issue.
Keeping processes resident in memory also can be a big improver of performance... you aren't going to get a clean comparison of JSP to straight CGI if you aren't using mod_perl or something similar.
Perl does a lot of jobs well; I think it is much more suited to 'batch' type processing than is java... for example, grab some data out of a database, drop it into an XML file. You then pass that file through a XSLT filter(s); get out some pregenerated HTML, marked up with a bit of javascript. That tends to be seriously scalable... and easy to support and debug. 'Use the right tools for the job at hand' is what I would have told them; sometimes that tool is Java and JSP... but often its not.
-
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.
|