Another thing that is nipping at your heels in the way of CPU usage is your means of displaying a status. (You could use Curses, but why bother?). The problem here is buffering is on. Since buffering is on you are having to overflow the buffer before anything gets dumped to your terminal, thanks to \r your terminal then proceeds to run through a buffers worth of lines (last I checked on on my linux box it was 2kb), and then display the last one. Not so efficient. $|++ And so you don't need to print a status update every round the loop, you eyes cannot see much more than 26 fps :-P

--
perl -pe "s/\b;([mnst])/'\1/mg"

In reply to Re: Is this the most efficient way to monitor log files.. by belg4mit
in thread Is this the most efficient way to monitor log files.. by Rhodium

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.