What is a better method for this.

Hi zer, See the below comparison using Array::FileReader, Slurp, File::Content modules and do function

use Array::FileReader; use Slurp; use Benchmark 'cmpthese'; use File::Content; cmpthese(-1, { Array => 'tie @foo, Array::FileReader, "test.txt"', Slurp => 'my @array = Slurp::to_array("test.txt")', do => 'do {local $/, "test.txt"}||die ($!)', Content => 'my $o_fil = File::Content->new("test.txt")', }); __END__ Rate Slurp Content Array do Slurp 3.94/s -- -100% -100% -100% Content 997/s 25229% -- -82% -100% Array 5467/s 138774% 448% -- -99% do 466126/s 11839502% 46643% 8425% --

Capacity of test.txt file is nearly 800KB

Regards,
Velusamy R.


eval"print uc\"\\c$_\""for split'','j)@,/6%@0%2,`e@3!-9v2)/@|6%,53!-9@2~j';


In reply to Re: Reading from large files by Samy_rio
in thread Reading from large files by zer

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.