I agree, the best solution is to not get into the situation in the first place. However, the script can't run 100% (bugs, remote server downtime, etc) and the files are always arriving (and the amount is expected to triple over the next few months). Plus the files tend to arrive in 'bursts' and not evenly spread out.

It just took 5 hours to move the 40,000+ files off the box and I believe >75% of the time was disk IO (running slowly via OS and number of files) from copy, rename, and delete. Just looking at the problem at that level I can't help thinking there is a better way to deal with it than what I am currently doing.

Fendaria

In reply to Re^4: File::Copy and file manipulation performance by Fendaria
in thread File::Copy and file manipulation performance by Fendaria

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.