There is an
example of using the Benchmark module
to compare different algorithms at
this node on
searching for an array index.
One difficult part of benchmarking
is keeping track of what you have changed, and what
effect these changes had. Here is one way to do it:
First, isolate the part of your code that needs
improvement in a subroutine.
Then, create new subroutines with different names
to try different approaches.
Preserve the different implementations of the subroutine
in the program. This ensures that you don't accidentally
change something else in your code that ruins your
comparison data. The Benchmark node mentioned above
shows an example of this approach.
If you keep your subroutine short, it is easy for
other people, such as Perl Monks, to help
speed up your code.
It should work perfectly the first time! - toma
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.