Under mod_perl, the perl code gets loaded once, and lives for the lifetime of the Apache handler process. (Apache forks off several children for handling requests). That is, the time it takes to load modules is a one-time hit.

I seriously doubt that you're going to find a measurable difference by splitting common code into a .pl (or .pm) that both scripts load, unless you're doing something that kills the handler process. When the handler dies, Apache/mod_perl has to set up a new one from scratch.

Still, benchmarking is the way to prove this. Even if there's not any difference, it's a good skill to have within reach.

In reply to Re: Improving PERL Performance by dws
in thread Improving PERL Performance by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.