...optimizing for CPU cycles in a language running in a 10-year old VM is rather silly.
Depends on how you're optimizing, of course. It looks to me like you're mainly railing against all those useless micro-optimizations (like using map EXP, vs MAP { EXP }).
But just choosing a sane algorithm for the job can easily reduce the time to run by many orders of magnitude, even if the algorithm is purely CPU bound. In that case, and if the dataset is large enough, CPU cycles obviously DO matter.
IOW "We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil."
-
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.
|
