It feels wrong because it is wrong. :)

The way to make your CGI faster is to have it compile once and stay in memory-- hence mod_perl and the like. No other optimization can beat that.

But your idea for a way of working is interesting, and exists for a reason. Probably just not this reason. It allows for things like Caillte's example of a program that is stored non-traditionally, or even mutates itself without having to restart. It allows existing scripts to be called from new scripts without having to incorporate their internals into your new script. It probably allows for lots of things, I just can't see using it to make a CGI load faster-- since it is fastest to not load the CGI at all (or, really, to load it once and leave it there).

And if your CGI is so huge that it is noticable each time it loads and mod_perl is just not an option, maybe you could break your large script into separate smaller scripts, isolating common elements into a module that can be used from each script. But in practice that may not be any more fun that what you've proposed.

In reply to (ichimunki) Re: Saving compile time by running subroutines as separate files with 'do' by ichimunki
in thread Saving compile time by running subroutines as separate files with 'do' by George_Sherston

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.