The IO involved in opening/closing/reading/writing those files is probably where you are spending the most of your time in those benchmarks. Since you're doing the same amount of IO in both test, it should affect which one is faster, but it does affect the ratio of sped between the two tests (just like adding a sleep(1) to both makes them both equally sucky)

If you really want to test *only* the CSV time, you can read from a tied filehandle that's really just a string in memory; and write to a tied filehanlde that just throws away the data you write to it.

take a look at Tie::FileHandle::Base the replies to this post as a place to start

In reply to Re: Benchmark comparison of Text::xSV and Text::CSV_XS by hossman
in thread Benchmark comparison of Text::xSV and Text::CSV_XS by jZed

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.