See if it is faster reading big chunks at a time, like this simple test case (of course, modify it for your file).
This only runs the regexes once for each chunk, instead of once per line. 

#!/usr/bin/perl

# https://perlmonks.org/?node_id=1221282

open my $fh, '<', \<<END;
###### test.txt########
sample AA
sample BB
Not sample CC
good boy
good yyy
bad aaa
END

local $/ = \1e6; # or bigger chunk depending on your memory size
while(<$fh>) # read big chunk
  {
  $_ .= do { local $/ = "\n"; <$fh> // ''}; # read any partial line
  push @sample, /^sample\s+(\S+)/gm;
  push @good, /^good\s+(\S+)/gm;
  }
close($fh);
print "sample = @sample\n  good = @good\n";

[download]

Outputs: 

sample = AA BB
  good = boy yyy

[download]

In reply to Re: About text file parsing by tybalt89
in thread About text file parsing by dideod.yang

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.