in reply to (jeffa) Re: Optimizing existing Perl code (in practise)
in thread Optimizing existing Perl code (in practise)

The fastest script in the world is worthless if a change in your
system's directory structure breaks your code and you can't fix it.

If you bother to optimize for anything, do it for maintainability
But never forget "monitorability".

Unless your script is being called to do huge jobs, or your resources
are very restricted (Sparc Ultra 1 or Intel 486, etc.) optimization for
speed is not usually that big an issue.

However, thorough and correct logging of events, meaningful commentary
in the script itself, reusability of the code; these will all help
with maintainability.

  • Comment on Re: (jeffa) Re: Optimizing existing Perl code (in practise)

Replies are listed 'Best First'.
Re^3: Optimizing existing Perl code (in practise)
by Aristotle (Chancellor) on Aug 19, 2002 at 11:07 UTC
    Another, and I think far more common case, where optimization for speed is rightfully desirable would be the code that drives a dynamic website. See perrin's impressive eToys success story for an admittedly extreme example; when you're facing a million pageviews an hour, you don't want your code to be wasting time, but even much lesser loads make speed an important goal. Nevertheless, of course, it does not override the factor of maintainability.

    Makeshifts last the longest.

[reply]
      I agree. But wouldn't you concider that a "huge job"? - cybear
[reply]

In Section Seekers of Perl Wisdom