cocoaforge

Downloading large files, > 25MB with a buffer size of anything other then 128, it fails, stopping at exactly 22.7MB each time, everytime.

I tried buffer sizes of 512,1024,4096,16384 and all have same results, download stops at 22.7MB and the maximum throughput at anytime is 640.0KB/s. If i leave the buffer size at 128, it downloads at < 80KB/s

I could go to the command line and use secure copy (scp) and these files download at ~10MB/s (100Mbps switch between the computers)

I tried both v2.4 and v2.5, on a PowerBookG4 running clean install of Tiger.

cheers

I also tried the sftp command line client.

/volume01/video/movies/KofH/koh.cd1.av 100% 700MB 8.4MB/s 01:23

Since scp and sftp use different methods when using version 2 of the protocol, i figured this is more valid test.

cheers

Ok, according to the sftp man page, its default buffer size is 32768 bytes. So that is 256kilobit [32768 / 1024 * 8] ...

Using a buffersize of 256, downloads no longer fail, but I was only able to achieve a maximum throughput of ~1.5MB/s, while command line sftp will max-out the 100Mbit pipe at about 8-10MB/s

After using Cyberduck(v2.4 & 2.5b1) more frequently now, I find large downloads, anything greater then 22.7MB, start failing for me no matter what the buffer size. Even at 128 Kilobits...

Is anyone else seeing the problem I am having? Or is just my computer?

fortunately, PHP scripts and text files are small and the majority of the use of Cyberduck works...

joe.roback wrote:Downloading large files, > 25MB with a buffer size of anything other then 128, it fails, stopping at exactly 22.7MB each time, everytime.

I tried buffer sizes of 512,1024,4096,16384 and all have same results, download stops at 22.7MB and the maximum throughput at anytime is 640.0KB/s. If i leave the buffer size at 128, it downloads at < 80KB/s

I could go to the command line and use secure copy (scp) and these files download at ~10MB/s (100Mbps switch between the computers)

I tried both v2.4 and v2.5, on a PowerBookG4 running clean install of Tiger.

cheers

I do not experience any of these problems of aborted downloads over my cable modem. (v.2.5.2) . But I do experience slow downloads at 128. I gather changing the buffer size didn't help you much.

Quack wrote:

joe.roback wrote:Downloading large files, > 25MB with a buffer size of anything other then 128, it fails, stopping at exactly 22.7MB each time, everytime.

I do not experience any of these problems of aborted downloads over my cable modem. (v.2.5.2) . But I do experience slow downloads at 128. I gather changing the buffer size didn't help you much.

I just started using Cyberduck 2.6.2 in my MacBookPro, and I'm pulling files via SFTP from a friend's Red Hat Linux system on the same subnet. I too ran into the size limit, and every file I tried to pull from the server stopped at 22.8 MB. If I resumed, the connection would pull down another 22.8 MB of the same file.

This does not happen when I'm downloading from a Solaris 9 server, out on the Internet.

There is plenty of local disk space, so that's not the problem. I did play with buffer sizes, too, and that didn't matter.

Clearly there's a limitation on something within CyberDuck that's causing this. Perhaps it has something to do with being on the local subnet?

EDIT: Oh yeah, I can run SFTP from the command line and it pulls the same files down, no problem.

I had a very similar problem, but I solved it by using ethernet instead of airport, I don't understand why it works now

manul wrote:I had a very similar problem, but I solved it by using ethernet instead of airport, I don't understand why it works now

Mine was connected via the ethernet port, as was the other machine.