We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil. (Donald Knuth)
Though this statement is not applicable in all situations it certainly is in this one.

Why do you think that "optimiz<ing> it by having _as many_ files as possible in the 'wanted' function would affect the performance? The only thing here you could call (minimal) "overhead" is the repeated calls to "wanted", but that's just the price you pay for using File::Find.

Why do you think that the OS would "move(...) the files all together in _one shot_ or at least in big chunks"? It moves them file by file.

Update: If you perceive performance differences between your perl version and a shell based equivalent, that's because File::Copy moves a file by
  1. opening the target for writing
  2. reading from source and write to the target
  3. unlinking/deleting the source
Depending on OS and filesystem this is less then optimal but also not OS dependent.

If that's no concern you could push the files found by "wanted()" into an array (or better yet use File::Find::Rule, which doesnt have this clunky callback interface) and feed that to the systems "mv", using proper quoting.


holli

You can lead your users to water, but alas, you cannot drown them.

In reply to Re: Optimizing files' moving with File::Find & File::Copy modules by holli
in thread Optimizing files' moving with File::Find & File::Copy modules by Anonymous Monk

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.