The main time consumption of your processing is in the file IO, ie. (as you indicate) the line-by-line parsing, plus writing & generating CRC on an external file;
Is this necessary? Couldn't you just read the transactions one-by-one from the file, and run the CRC-calculation on each XML-trans in memory ?? -- As in (untested) :
#!/usr/bin/perl -w
use strict;
use warnings;
use String::CRC32; ### for instance
my $XmlData = <<XML_DATA;
<Transaction>
<MessageCode>100</MessageCode>
<ToAccountNo>12989898900</ToAccountNo>
</Transaction>
<Transaction>
<MessageCode>200</MessageCode>
<ToAccountNo>24536485582</ToAccountNo>
</Transaction>
XML_DATA
open my $XmlFile, '<', \$XmlData or die "Can't open XML file: $!";
$/ = "</Transaction>"; ### one trans at-a-time
while ( <$XmlFile> ) {
my $crc = crc32($_);
### & do whatever needs TBD with the $crc ...
}
Allan Dystrup
-
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.
|