I guess that you are loading large amounts of file contents into memory, which takes some time.

But since you have only one lookup, you don't have to store the values - you could compare them on the fly: 

for my $filename (@repos){
    if ($input eq read_file($filename)){
        print "File $filename matches\n";
        exit;
     }
}
print "No match";

[download]

If the files are rather large you can optimize the process further my just reading the first $N bytes (let's say 512) and compare them, and only if these first bytes are identical read all of the file.

Or you could just dump the files into a database and let the database build an index, then all you have to do is query the database. If your repo doesn't change too frequently that's probably the fastest solution.

Perl 6 in German -- Difficult Sudoku

In reply to Re: Efficent Text Checking by moritz
in thread Efficent Text Checking by neversaint

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.