Both reading the log and updating the database are apt to be I/O bound, so threads or a forked process make sense (particularly if the log and db are on different spindles). I'm not too familiar with perl threads, so lets fork the db updater with a pipe from the parent to ship data over,
sub update_db {
# ...
}
sub mung_logline {
# ...
}
pipe my($rd, $wr);
my $cpid;
{
$cpid = fork;
die $! if not defined $cpid;
unless ($cpid) {
close $wr;
my $dbh = connect(,,,);
while (<$rd>) {
update_db( $dbh, $_);
}
close $rd;
exit 0;
}
}
close $rd;
{
open my $fh, '<', '/path/to/log.file' or die $!;
while (<$fh>) {
$_ = mung_logline($_);
print $wr $_;
}
close $fh;
}
close $wr;
That leaves out your desire to accumulate a large instruction, possible autoflushing of the pipe, @SIG{'CHLD','PIPE} handling and/or
wait, and much error handling. Take it as a skeleton.
It may be best to produce a $sth = $dbh->prepare('whatever ?') with placeholders right after the $dbh is obtained. Then you can pass the $sth already set up to update_db, instead of $dbh.
-
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.