in reply to Using Devel::Profile output to know what to do next

In almost all cases, the database is what needs optimizing, not your script. Remove dead records and optimize your tables often; set up indexes for large, high volume queries; and make sure that you're not using a series of inefficient queries when one query will do. Also, use the smallest field size possible for each piece of data, and stay away from variable length fields unless you really have to use them. If you do use them, always put them at the end of the record, and be sure to optimize your tables even more often to remove dead space.
  • Comment on Re: Using Devel::Profile output to know what to do next

Replies are listed 'Best First'.
Re^2: Using Devel::Profile output to know what to do next
by BrowserUk (Patriarch) on Jun 08, 2005 at 03:45 UTC

    Don't guess --profile.


    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
    "Science is about questioning the status quo. Questioning authority".
    The "good enough" maybe good enough for the now, and perfection maybe unobtainable, but that should not preclude us from striving for perfection, when time, circumstance or desire allow.