I think if you find yourself trying to optimize how a configuration file is loaded, you might be barking up the wrong tree for improvements of the code's efficiency. Do you know this to be a bottleneck? Or are you just guessing that it is? If startup time is the problem, maybe converting the script over to mod_perl could be more of a long-term solution.

I'm not saying you couldn't shave a few nanoseconds off startup time by tweaking how your config file gets loaded. I'm just saying that nanoseconds are small, and you may find microseconds and milliseconds hiding in other places instead.


Dave

In reply to Re: Using Perl files for options versus flatfiles? by davido
in thread Using Perl files for options versus flatfiles? by AK108

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.