Just in theory:

If your users are calling many scripts in a session you could also consider using wrappers to start the perl-binary only once.

First start would compile all scripts (as subs) and at termination go into background and "freeze".

The next wrapper-call would just need to find and "defreeze" the process and call the already compiled sub.

The drawback would be the constant memory consumption of an independent perl process per user and like in mod_perl you have to be very prudent about any side-effects of your scripts.

Cheers Rolf

Update

Seems like MLX's suggestion of "persistent perl" follows more or less these ideas ... :)

In reply to Re: Techniques to cache perl scripts into memory ? by LanX
in thread Techniques to cache perl scripts into memory ? by fx

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.