In addition to advice regarding only opening the output files once, an extra speed increase could be gained by using unpack instead of substr:
use strict; use IO::File; $|++; my $sourcefile = 'data.txt'; my @possibletargets = qw(1 2 3 4 5); my %tgthandles = (); foreach my $target (@possibletargets) { my $fname = 'form_' . $target . '_record.txt'; $tgthandles{$target} = IO::File->new(">>$fname"); } open(REPORTS, $sourcefile); while(<REPORTS>) { my $line = $_; my $id = unpack("A1A*", $line); my $fh = $tgthandles{$id}; print $fh $line; } close(REPORTS); foreach my $key (keys(%tgthandles)) { $tgthandles{$key}->close; }

In reply to Re: ?? Blazes under Linux; crawls under XP & Win2K... by markwx
in thread ?? Blazes under Linux; crawls under XP & Win2K... by WordWeaver

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.