Re^2: Optimizing files' moving with File::Find & File::Copy modules

My guess is that the OP wants to cut down on the number of processes - which many monks will tell you is "bad".

Personally, if I were to move within the file system, I would call rename (and use an external find to find the files); if I were to move from one filesystem to the other, I would realize the entire process is likely to be disk I/O bound, so I wouldn't care about the process calls.

Comment on Re^2: Optimizing files' moving with File::Find & File::Copy modules Select or Download Code

Replies are listed 'Best First'.
Re^3: Optimizing files' moving with File::Find & File::Copy modules by holli (Abbot) on Nov 17, 2009 at 14:29 UTC
What processes? Neither File::Find nor File::Copy spawn any external processes. holli You can lead your users to water, but alas, you cannot drown them.	[reply] [d/l]