Not really hints on how to optimise, more hints on how to avoid a lot of problems with it. Make sure your code works beforehand, and use unit tests such as Test::More, or Test::Harness to make sure your code remains working whilst you're torturing it. Yes, there are rather a lot more of them to chose from if you look.. this is one wheel important enough that it's worth having a few choices as to what colour you want.
Oh, and make sure you know the output from your profiler. There's nothing worse than optimising the wrong part.
<CITE>"Premature optimization is the root of all evil."
- Donald Knuth</CITE>
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- 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
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||