FAQ 3.16 How can I make my Perl program run faster?

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

This message is one of several periodic postings to comp.lang.perl.misc
intended to make it easier for perl programmers to find answers to
common questions. The core of this message represents an excerpt
from the documentation provided with Perl.


3.16: How can I make my Perl program run faster?

    The best way to do this is to come up with a better algorithm. This can
    often make a dramatic difference. Jon Bentley's book *Programming
    Pearls* (that's not a misspelling!) has some good tips on optimization,
    too. Advice on benchmarking boils down to: benchmark and profile to make
    sure you're optimizing the right part, look for better algorithms
    instead of microtuning your code, and when all else fails consider just
    buying faster hardware. You will probably want to read the answer to the
    earlier question ``How do I profile my Perl programs?'' if you haven't
    done so already.

    A different approach is to autoload seldom-used Perl code. See the
    AutoSplit and AutoLoader modules in the standard distribution for that.
    Or you could locate the bottleneck and think about writing just that
    part in C, the way we used to take bottlenecks in C code and write them
    in assembler. Similar to rewriting in C, modules that have critical
    sections can be written in C (for instance, the PDL module from CPAN).

    If you're currently linking your perl executable to a shared *libc.so*,
    you can often gain a 10-25% performance benefit by rebuilding it to link
    with a static libc.a instead. This will make a bigger perl executable,
    but your Perl programs (and programmers) may thank you for it. See the
    INSTALL file in the source distribution for more information.

    The undump program was an ancient attempt to speed up Perl program by
    storing the already-compiled form to disk. This is no longer a viable
    option, as it only worked on a few architectures, and wasn't a good
    solution anyway.


Documents such as this have been called "Answers to Frequently
Asked Questions" or FAQ for short.  They represent an important
part of the Usenet tradition.  They serve to reduce the volume of
redundant traffic on a news group by providing quality answers to
questions that keep coming up.

If you are some how irritated by seeing these postings you are free
to ignore them or add the sender to your killfile.  If you find
errors or other problems with these postings please send corrections
or comments to the posting email address or to the maintainers as
directed in the perlfaq manual page.

Note that the FAQ text posted by this server may have been modified
from that distributed in the stable Perl release.  It may have been
edited to reflect the additions, changes and corrections provided
by respondents, reviewers, and critics to previous postings of
these FAQ. Complete text of these FAQ are available on request.

The perlfaq manual page contains the following copyright notice.


    Copyright (c) 1997-2002 Tom Christiansen and Nathan
    Torkington, and other contributors as noted. All rights

This posting is provided in the hope that it will be useful but
does not represent a commitment or contract of any kind on the part
of the contributers, authors or their agents.

Site Timeline