Everyone has already pointed out the advantages of dbms and databases. But if you just need to process the files once, it is probably most efficient to hash your search strings instead. Like this (untested):
# Build a hash lookup for things I want, defaulting to not there
my %found;
my @search;
foreach my $item (@timearray) {
my $id = "$NETID\|$month\/$date\/$year\|$item\|";
push @search, $id;
$found{$id} = "||$item||";
}
# Scan the file for them
my $file = "/PHL/data1/PHL/tmp/ECL_STAT";
open(ECL_STAT, "< $file") or die "Cannot read $file: $!";
while (<ECL_STAT>) {
chomp;
if (/(([^\|]+\|){3})/ and exists $found{$1}) {
$found{$1} = $_;
}
}
# Build output array
push @ECL, map $found{$_}, @search;
Now you only need to scan once, and only build in memory data structures for the actual data you are looking for.
(Which is coming in the order you are looking for it in. This code would be easier if I could assume that order didn't matter.)
-
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.
|