comment on

Here are some of the things I think you'll want to know as you write a Perl script to do what your shell script does:

Start with "use strict;use warnings;". Read Use strict and warnings for details. You'll have to use my because of this.
You'll probably want a loop that starts with "while ( my $line = <> )". You may want to use open.
chomp
split

Regular expressions will be very useful, so have a look at perlretut. For example:

if ( $line =~ /(\d+:\d\d):\d\d (?:GMT|SAST)/ ) {
    my $the_hour_and_minute = $1;
}
[download]

I'd be tempted to use the range operator to capture things between /^vmstat/ and /^END/, but using a flag as you have already will still work.
print, warn, die

I'll note also that vmstat has a -n option which causes it to output the header only once. You could send that through tail before it ever gets to the log, and your processor would not have to deal with those lines at all.

In reply to Re: Extracting data from a messy file (slow performance) by kyle
in thread Extracting data from a messy file (slow performance) by acidblood

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Perl Monk, Perl Meditation
	PerlMonks