I can see several things in there that you might want to do spot performance analysis on. For example, how long does 
  $galinfo = LoadFile ("galinfo.yaml");

[download]
take? Run down the code, and any place you're doing something that you can't easily characterize behavior on, throw some timing code around it. You can emit the raw timing info in an HTML comment, and get at it via View Source.

Another thing to note, if you aren't clear on it, is that putting a use inside a conditional doesn't make the use conditional; it just limits scope.

You might also consider whether you really need File::stat, or can make do with built-ins.

In reply to Re^5: Startup cost, CGI performance by dws
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.