You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using Cyberduck 3.0.3 (4189), OS X 10.4.11, Java 1.5.0_16
FTP'ing a single large file to my Mac causes Cyberduck to chew 12 to 20% of my CPU, according to Activity Monitor. By comparison, the same file FTP'd with curl uses 0.7% for curl and 3% for Terminal, a total of 3.7%. The average throughput for Cyberduck is about 30 KB/sec. For curl, it's about 45 KB/sec.
When I start other FTP streams, Cyberduck's CPU usage goes up even more while the total throughput barely increases (this over 20 Mbps fiber service).
Now, granted, these CPU percentages are a bit high because my Power Mac is slow. But they are proportional on a faster Mac too. (300 MHz G3 vs 1.5 GHz G4). Cyberduck seems to be wastefully chewing cpu cycles instead of getting work done.
Please improve Cyberduck's efficiency and (more importantly) throughput.
Thanks!
The text was updated successfully, but these errors were encountered:
Just another data point... ftp'ing the same large file from a friend's server in Florida. I'm in New Jersey. The route between us looks to be very clean today.
Using Cyberduck 3.0.3 (4189), OS X 10.4.11, Java 1.5.0_16
FTP'ing a single large file to my Mac causes Cyberduck to chew 12 to 20% of my CPU, according to Activity Monitor. By comparison, the same file FTP'd with curl uses 0.7% for curl and 3% for Terminal, a total of 3.7%. The average throughput for Cyberduck is about 30 KB/sec. For curl, it's about 45 KB/sec.
When I start other FTP streams, Cyberduck's CPU usage goes up even more while the total throughput barely increases (this over 20 Mbps fiber service).
Now, granted, these CPU percentages are a bit high because my Power Mac is slow. But they are proportional on a faster Mac too. (300 MHz G3 vs 1.5 GHz G4). Cyberduck seems to be wastefully chewing cpu cycles instead of getting work done.
Please improve Cyberduck's efficiency and (more importantly) throughput.
Thanks!
The text was updated successfully, but these errors were encountered: