4 hours to upload 40Mb files, not done yet...

[alainc.]

I'm trying in order to do some work to upload Gallery2 (multi folder),
And don"t know how many attempts I have done but I'm fighting for 4 hours now, and not winning the case...
I've tested my connection, the host availability, everything is fine, there's something very wrong with cyberduck...
Plus, a lot of files/folders are not transmitted, I've to check them one after one..
I think I'm going to give up on CB, it's a great tool, but to much trouble, I can't afford to loose all this time waiting to get my files uploaded
I'm considerating another FTP client

[alainc.]

7 hours, and upload stops before completing...
Too much, I give up, and offer Cyber Duck a tour of the trash bin..
Too bad
Alain

[jwkuehne]

I have similar problems on my first attempt with Cyberduck. With straight sftp from Terminal I can transfer the cyberduck disk image at 3Gb/sec on our network, but only 256K/sec from Cyberduck 2-1.7.3

Something is very wrong.

[kspeakman]

I have similar problems on my first attempt with Cyberduck. With straight sftp from Terminal I can transfer the cyberduck disk image at 3Gb/sec on our network, but only 256K/sec from Cyberduck 2-1.7.3

Something is very wrong.

After seeing this thread, I also just did a comparison. I'm on a 100 Mbit LAN. Using command-line SFTP, I was getting speeds of 10 MB/s (local LAN connection), but using a CyberDuck SFTP connection to the same server, and the same file, it seems to be rate-limiting at 1 MB/s. I tried the transfer several times with both clients and got the same results.

I wonder... Is this a limitation on the sftp code they are using or does CyberDuck impose a limit of some kind?

Kasey