Please check the version of commons-io library in OODT. If it is old it may well be the case that it uses a less-than optimum copy strategy. I think we've seen stuff like this before. Currently we are using commons-io 1.4 which was released on 20th Jan 2008!!! http://search.maven.org/#artifactdetails|commons-io|commons-io|1.4|jar
The most recent version can be located at http://search.maven.org/#artifactdetails|org.apache.commons|commons-io|1.3.2|jar Version 1.3.2 (please note change in groupID) was released on 9th Oct 2012. I bet an upgrade would speed things up dramatically... #JiraIssue On Fri, Oct 21, 2016 at 11:35 AM, Tom Barber <tom.bar...@meteorite.bi> wrote: > Hello folks > > I'm asking here just incase someone knows a reason why this is a bad idea: > > We have a bunch of large files on a slow NFS mount which we're ingesting in > bulk. Its using the LocalDataTransferer to do the ingestion move and in > that code all the move calls are really file copies. > > As you'll all know in doing a copy the drive is actually writing bits to > disk, where as doing a move is just moving the file pointer. > > Is there a reason why the moveFile method actually uses > FileUtils.copyFile() before I try FileUtils.moveFile() ? > > Because 1 min for a copy vs 0.06 seconds for a move is far more preferable. > > Thanks > > Tom > -- http://home.apache.org/~lewismc/ @hectorMcSpector http://www.linkedin.com/in/lmcgibbney
