Beefy Boxes and Bandwidth Generously Provided by pair Networks
XP is just a number

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
I have a directory containing 50,000 text files for a total of 1.5GB of data.

I want to quickly grep it for a Perl regular expression, and get a list of occurances by file name and line number.

I could just:

use strict; use warnings; use File::Find; my $regexp = shift @ARGV; sub process_file { open FH, $File::Find::name; my $count = 0; while (<FH>) { if ( print $File::Find::name . " " . $count . "\n" if /$regexp/; $count++; } close; } find(\&process_file, @ARGV);

(or indeed just use unix grep)

...but speed is important and disk space is cheap.

My vision is to somehow run a process (overnight) that creates a large index of regexp-beginning vs files. (Possibly even 30GB+ if it would be useful.)

The index could cache the results for all possible starting prefixes every regexp to some depth limited by the index size. This would allow the search algorithm to skip some of the work.

I realize search is a hard problem, but has anyone got any ideas about:

Architecture? I'd have to reimplement or modify Perl's regexp parser to do this right? No way to tokenize a regexp to get a prefix?

CPAN modules that might be useful?

Caching algorithm for the index?

Alternative solutions (open source only)? Similiar projects?

General feedback about the idea?


In reply to Searching local files by tomazos

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • 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.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others having an uproarious good time at the Monastery: (3)
As of 2023-10-03 23:40 GMT
Find Nodes?
    Voting Booth?

    No recent polls found