Some opinions:
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?
print statements (sometimes in combination with YAML - never with Data::Dumper). make test. I seldomly benchmark programs I write, but I do benchmark
theoretical cases.
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.
Abigail
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
