The YAML read takes about .5 seconds in this case -- it's there in the timings in my original post, and has been discussed already. That's the single big chunk of time, other than loading the modules. However, the application depends on manual editing of that file as well as automated reading/writing, so changing it to a binary format would require me to develop a whole new application for the "manual editing", so that's low on my priorities.

Is File::stat particularly big? I could work around dropping that. I'll look/test that; I'm not hopeful, though, the .pm file is only 2.8k, plus it pulls in Class::Struct which is 18.7k. I guess if nothing else pulls in Class::Struct that might be of some significance.

In reply to Re: Re^5: Startup cost, CGI performance by dd-b
in thread Startup cost, CGI performance by dd-b

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.