It is my belief that you could get better by not considering guesswork if you are serious into optimization.
You must consider facts and you must work on what you can control, so rethinking your algorithm would be the first approach.
Then you can benchmark your different solutions and choose the one that performs better.
After choosing the best algorithm you can dwell upon turning your code unreadable by using some of the good old techniques that you must be familiar with from your C background, such as lookup tables or, even deeper, loop unroling, less function calls ....
Your desk is lacking an algorithms book :)

--
olus

In reply to Re: How do I get better at thinking about optimizing my Perl? by olus
in thread How do I get better at thinking about optimizing my Perl? by amarquis

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.