It looks to me like you've shifted the burden of your processing away from looking at each log file line more than once to looking at each comparison of each report more than once. I'm not surprised this is a lot slower; you've probably tripled the number of comparisons.

In particular, when you have an operation such as this one in a loop:

@comparisons = split(" ", $reports{$rep}[0]);

you should ask yourself, "Self, why not just stick this information in the data structure as an array when I generate it?"

Without seeing where %reports comes from, I can't give you any more specific ideas. If you could classify each line with only one comparison, though, I bet you'd see a better speed gain.

In reply to Re: Pattern matching speed by chromatic
in thread Pattern matching speed by Anonymous Monk

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.