Hi Not sure if setting a sentBufferSize on the client helps?
ftpClient.sentBufferSize=8192 Its -1 by default. Check the API of Commons Net FTP to see if it has any impact. org.apache.commons.net.ftp.FTPClient And maybe there is other options you can set on the ftpClient to speedup upload. Also you can enable TRACE logging on the org.apache.camel.component.file.remote name to ensure that the file is using a stream to upload it. On Wed, Mar 13, 2013 at 4:49 PM, GarethHughes <gareth.hug...@hp.com> wrote: > Can anyone point me in the right direction to solve this performance problem. > We need to move large files around our system and ultimately upload them to > a remote FTP server. I am using the Claim Check EIP to move the files around > the system so immediately prior to performing the FTP upload to the remote > server I extract the file from an Oracle database to the local file system > using the largeFileService bean as shown below: > > > > So as you can see I pass a stream to the next stage of processing which is > to upload to the remote FTP server thus.... > > > > I also have streamCache enabled on my Camel context. > > Problem is, the FTP transfer takes an inordinately long time. A manual > transfer of the same 33Mb file to the same FTP server takes 2.88 seconds. > Whereas the Camel route(s) above managed to transfer just 4Mb in 15 minutes > before I kill it off. > > Am I missing something blindingly obvious here? It feels like a buffering > issue. > > Thanks > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Performance-problem-uploading-to-remote-FTP-using-Stream-tp5729125.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
