I had a similar problem earlier where I had to speed up the text file parsing part of my application.

Without really going through your code, here are a few tips that may or may not come handy.

  • I recommend Devel::NYTProf for profiling. It gives you a very nice color-coded, line-by-line report on your code that you can use to figure out exactly where the bottlenecks are.

  • I found that substr is the fastest way to parse data out of lines that consist of fixed width fields only.

  • tr/// is faster than s///. (I don't know whether this is applicable here, though.) Anyway, the fewer regexps, the better.

  • In the inner conditional of your filterLog function, do you really need to test the existence of your $opts{} variables?

    • In reply to Re: How to improve speed of reading big files by kikuchiyo
    in thread How to improve speed of reading big files by korlaz

    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.