The filesystem, system caches and disk DD's have access to far more and far better information, from all concurrent activity--not just those processes using your mechanisms--upon which to decide what order to read and write things and when.

I personally believe that this seems to be the general consensus as of the answers that popped up in this thread. I may well stand corrected out of trusting the expertise of you all. But the impression of things getting so awfully slow with parallel transfers was so strong that I'd like to at least do some (more) experiment and to this end...

However, were I to write something along these lines, my starting point would be Jenda's extremely useful Win32::FileOp, which gives you direct access to the OS's own MoveFile and CopyFile functions

...I will certainly try Win32::FileOp in the first place to do the experiment in a more controlled way! Thank you for the suggestion!

--
If you can't understand the incipit, then please check the IPB Campaign.

In reply to Re^2: Seeking general directions for a Windows specific app by blazar
in thread Seeking general directions for a Windows specific app by blazar

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.