Instead of worrying about the small difference between both methods, I'd worry about the tiny throughput you have. Writing the numbers 1 to 100 each on their own line takes 292 bytes. You do 3.51 times a second. Which means you're writing about 1kb/sec.

I'd focus on finding out why you can write only 1kb/sec instead of worrying about the 8% difference in speed. For the recond, on my box, 'File1' is much faster than 'File2', but my 'File2' more than 25 times faster than your 'File1': 

         Rate File2 File1
File2 93.0/s    --  -68%
File1  294/s  216%    --

[download]
BTW, if I repeat the benchmark, the variation in results is more than the 8% difference you're measuring.

In reply to Re: File::Slurp Not As Efficient As OPEN / CLOSE by JavaFan
in thread File::Slurp Not As Efficient As OPEN / CLOSE by ~~David~~

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.