comment on

Choosing the right tool for the job, a digest.

If your application is CPU-bound, Perl will certainly be quite a poor fit, and be beaten by C (obviously) and most of the time, Java.

If your application is IO-bound (many are, be it network or disk IO), most languages will perform about the same.

In your case, most naive perl implementations will be slower than Java, being CPU-bound. However, the win may be in the development and maintenance time; after all if your program runs in 30 ms instead of 5 ms, that hardly makes any difference to you.

In reply to Re: Perl slower than java by wazoox
in thread Perl slower than java by Christian888

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.


laziness, impatience, and hubris
	PerlMonks