comment on

When do you reach the point of "OK, this has too many tests"?

My attitude to optimisation and benchmarking is neatly summarised by these two quotes:

"Premature optimization is the root of all evil in programming."
-- C.A.R. Hoare

Rules of Optimisation:
Rule 1: Don't do it.
Rule 2 (for experts only): Don't do it yet.
-- M.A. Jackson

Basically, CPU cycles are cheap. It's much more important to write clear elegant code that you can come back to in six months and still understand.

Most of the time you'll find that the most obvious clear code is more than fast enough. I only reach for Benchmark in the very few cases when this isn't the case.

In reply to Re: Benchmark testing by adrianh
in thread Benchmark testing by AcidHawk

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.


Your skill will accomplish what the force of many cannot
	PerlMonks