...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."

"What should it profit a man, if he should win a flame war, yet lose his cool?"

In reply to Re^7: CPU cycles DO NOT MATTER! by Joost
in thread CPU cycles DO NOT MATTER! by dragonchild

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.