Should I start building test/benchmark code into my future scripts for debugging purposes..?
As a general rule, no. It makes your code messy, and you'll
do a lot of work that you may not use at all.
What do other monks do for benchmarking/testing their scripts?
statements (sometimes in combination with YAML - never with Data::Dumper). make test
. I seldomly benchmark programs I write, but I do benchmark
When do you reach the point of "OK, this has too many tests"?
With about 150,000 tests in Regexp::Common, I say "never".
What other metrics do you measure (I.e. speed, memory)?
Several others, of which the most important is I/O. With
modern hardware, I/O is often a bigger bottleneck than
CPU speed or memory. But of course, it depends on the problem and what else is going on on the box.
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:
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||