RE: code optimization was: Trivia: Processor MHz

["Hall, Philip" <phall@xxxxxxxx>]

> More times than not, optimizing code reduces its readability.
> If what you are optimizing is already sub second, you are
> being counterproductive.

Sub-second for a function that gets called once or twice, yes. For a
function that gets called thousands of times, no.

Comments in the code are for readability, plus if you don't understand (and
understand I mean it's functional design, not guessing from looking at the
variable names :) the code you're about to try and optimise (whether it's
your code or someone else's) how on earth are you going to optimise it ?

> Only on the cpu challenged as400 does activity like this
> have a justification.

CPU challenged ? How many concurrent users can a Intel processor with any OS
(Linux, Windows, BeOS) running at 266Mhz cope with ?

As others have pointed out many times; it's making sure you're using the
right work with the right tool.
iSeries doing lots of DB work and servicing lots of users = right tool.
iSeries doing heavy computational work (such as image processing) = wrong
tool.

--phil