Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
As others have said:
  • Write it and optimise only if it needs it
  • Get your algorithms right first
  • Ninety percent of your code will be fast enough - only certain blocks may need tweeking.

    Case in point - on a recent project with over 1/2Mbyte of script and about 400 'instances' two 'instances' ran far too slowly. Most 'instances' ran in under 10 seconds while these two required 60 minutes, which was unacceptable.
    An analysis (See comments on monitoring) showed that we had the following:

       $thing = new thing;
       print $thing->result();
    All very well and good, but our class was heavily inherited and new executed no less than 60 lines of code, including multiple function calls. result went all the way up the tree to an AUTOLOAD handler. And all for a 10 line method

    So, about 120 lines of code (and about 20 @INC function calls) to do 10 lines of code.

    Time for some faster, locally optimised code AND VERY LOUD COMMENTS. Both in the local code and in the class which was being 'broken'. Nett result was a run time about 10 seconds. Which was acceptable for this project.
    Butlerian Jihad now!

    In reply to Re: Optimizing existing Perl code (in practise) by thoglette
    in thread Optimizing existing Perl code (in practise) by JaWi

    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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others scrutinizing the Monastery: (7)
    As of 2019-07-22 22:24 GMT
    Find Nodes?
      Voting Booth?
      If you were the first to set foot on the Moon, what would be your epigram?

      Results (21 votes). Check out past polls.