Compiling keywords can make a difference if you do all of them at once, before the loop.

#!/usr/bin/perl -w
use strict;

open WORDS, "<kwords" or die;
my %kwords=();
while (<WORDS>) {
    chomp;
    $kwords{$_} = qr/\b$_\b/m;
}
close WORDS;

my %found =();

for my $f (<abstract*>) {
    local $/;
    open FILE, $f or die "$f\n";
    my $text = <FILE>;
    close FILE;
    for (keys %kwords) {
        my $val = $kwords{$_};
        $found{$f} .= "$_ " if $text =~ /$val/;
    }
}

print "$_\t$found{$_}\n" for sort keys %found;

[download]

Assuming that the keywords are in a file, and each abstract is in a separate file, precompilation makes the search 30% faster (using 1000 test files, 300 words each, 3 random keywords in 2/3 of them).

In reply to Re: Compile the regex by dbwiz
in thread speeding up regex by dannoura

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.