Transfer Files actions takes a long time

We are using the Transfer Files action to copy a 100MB file between 1 unix machines.

Buildmaster is taking > 8 minutes to complete the copy, but using scp from one machine the copy only takes 5 seconds.

I would expect Buildmaster to take more than 5 seconds as it is probably copying to the Buildmaster Windows server as an intermediate step, but 8 minutes seems too long.

That is an usually long time... The xfer files action does does not do a direct xfer (you could of course shell script that), but that overhead is really high. Is it all on same network?

The xfer files action uses the Linux extension, which uses sftp over the ssh tunnel it establishes. Is there a way to test the network connection in the manner from my the buildmaster server?

The same file takes 65 seconds to be copied from the source unix machine to the Buildmaster Windows server (Windows server 2008 virtual machine, 2 CPU, 4GB RAM).

hi Dave,

We think a problem is with some connection overhead; we chunk/split files before transferring them... but we're still investigating what could be causing this.

We may email you some more info, as we have it.

So far we've been unable to reproduce this behavior. Our tests haven't shown any appreciable overhead when transferring a large file with BuildMaster.

What Unix (or Linux distro) are you using? Our testing is mostly done with CentOS 6+

We are using Solaris 10. It is possible the delays are being caused by poor performance of the Buildmaster server which is running as a virtual machine. I have raised a helpdek issue on our side to investigate as just copying the file with winscp from Solaris to Buildmaster takes 65 seconds which is too long.