Be slightly cautious when trying to parallelise disk IO. You can end up with some rather unexpected consequences. You can't change the laws of physics - a rotating platter and moving head still has to move to find data.

So if you start reading from mulitple points on the disk at once, you will create contention and slow down the overall result because of the seek time overhead. You will also make it harder for your OS to predict and prefetch data into cache, which can also reduce performance. Depends on what other workloads and limiting factors are present though - typically the storage subsystem is one of the slowest in your computer system

In reply to Re: Yet Another threaded find|grep perl utility by Preceptor
in thread Yet Another threaded find|grep perl utility by QuillMeantTen

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.