Ok, I can see why that would be slow. Without knowing more about the nature of the find and replace strings it's hard to suggest any specific solution that are guaranteed to help, but the following technique may help:
use strict;
use warnings;
my $source = <<STR;
I have a file with 50,000 lines of find and replace string.
For example
/Test/Sample/
/A/X/
Now i want to process the file with input file.
I have tried with usual method, it takes more than 1 hour.
Please advice.
STR
my $matches = <<STR;
/advice/advise/
/usual/the usual/
/lines/wobbles/
/file/flibble/
STR
my %replace;
open my $repIn, '<', \$matches;
while (<$repIn>) {
next if ! m{/([^/]+)/([^/]+)/};
$replace{lc $1} = $2;
}
close $repIn;
my $match = join '|', keys %replace;
open my $srcIn, '<', \$source;
while (<$srcIn>) {
s/($match)/$replace{lc $1}/eig;
print;
}
Prints:
I have a flibble with 50,000 wobbles of find and replace string.
For example
/Test/Sample/
/A/X/
Now i want to process the flibble with input flibble.
I have tried with the usual method, it takes more than 1 hour.
Please advise.
True laziness is hard work
-
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.