[ https://issues.apache.org/jira/browse/IO-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147904#comment-13147904 ]
Henri Yandell commented on IO-271: ---------------------------------- Should this be resolved as WontFix? > FileUtils.copyDirectory should be able to handle arbitrary number of files > -------------------------------------------------------------------------- > > Key: IO-271 > URL: https://issues.apache.org/jira/browse/IO-271 > Project: Commons IO > Issue Type: Improvement > Components: Utilities > Affects Versions: 2.0.1 > Reporter: Stephen Kestle > Priority: Minor > > File.listFiles() uses up to a bit over 2 times as much memory as File.list(). > The latter should be used in doCopyDirectory where there is no filter > specified. > This memory usage is a problem when copying directories with hundreds of > thousands of files. > I was also thinking of the option of implementing a file filter (that could > be composed with the inputted filter) that would batch the file copy > operation; copy the first 10000 (that match), then the next 10000 etc etc. > Because of the lack of ordering consistency (between runs) of > File.listFiles(), there would need to be a final file filter that would > accept files that have not successfully been copied. > I'm primarily concerned about copying into an empty directory (I validate > this beforehand), but for general operation where it's a merge, the > modification date re-writing should only be done in the final run of copies > so that while batching occurs (and indeed the final "missed" filtering) files > do not get copied if they have been modified after the start time. (I presume > that I'm reading FileUtils correctly in that it overrides files...) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira