Slow Performance...

Core FTP client questions and answers
Post Reply
SFSW
Posts: 9
Joined: Sat Dec 09, 2006 5:49 pm

Slow Performance...

Post by SFSW »

Is there a way to improve the upload/transfer speed with Core FTP? I have tried to change the buffer sizes and other settings with no luck. I can't seem to exceed about 45-50 KB/s no matter what I try. Oddly, other FTP programs can upload 2-3 times as fast (100-150 KB/s)... connecting to exactly the same server on the same computer using the same connection. Any help is appreciated, I enjoy the ease of use that Core FTP provides, but the performance seems to be very low.
SFSW
Posts: 9
Joined: Sat Dec 09, 2006 5:49 pm

Post by SFSW »

I tried changing those settings as suggested, no change in performance. It still peaks out at 44-45K maximum. I don't think SFTP is used with any of the sites I'm working with, only SSL. Any other possible options? The slowest speed I've ever encountered with another FTP program was about 75K, with nearly all others at 100K or faster. So I hope there's a way to at least double the performance of CoreFTP.
SFSW
Posts: 9
Joined: Sat Dec 09, 2006 5:49 pm

Post by SFSW »

Windows SSL didn't seem to make any difference. Likewise with the ANSI version, still only get about 40-45K maximum. It's almost like there's just something holding it back from performing up to speed. Other FTP programs seem to even retrieve server comments a lot faster. Maybe I'm doing something wrong in the settings, here's the configuration I'm using:

Under SSL Options:
AUTH SSL - Checked
AUTH TLS - Unchecked
SSL Direct - Unchecked
SSL Listings - Checked
SSL Transfers - Checked
Clear (CCC) - Unchecked

Open SSL - Checked
Windows SSL - Unchecked (tried this reversed as mentioned above, no difference)

PASV - Checked
SSH/SFTP - Unchecked
Use Proxy - Unchecked

Under the Connections section of the Options menu:
CPS Settings:
Max Recv - 2000000000
Max Send - 2000000000
Min Recv - 0
Min Send - 0
Connection Types:
Single Connection - Checked (everything else is grayed out)

Buffer Sizes (I've also tried this with 1024 for send and 8092 for received, just set it back to default after there was no improvement):
Send - 512
Received 512

Connection Retry
On - Checked
Count - 2
Retry Delay (secs) - 61

Keep Alive:
On - Unchecked
NOOP only - Unchecked
timer (seconds) - 15
Custom - Unchecked

PASV Connections for transfers - checked (everything below it unchecked)
Connection Timeout - 30 seconds
Fast connection - Checked
Show connecting window - Unchecked
Beep on sysop message - Checked
Allow auto password S/Key - Checked
maurert
Posts: 59
Joined: Tue Oct 10, 2006 12:18 pm

I experienced simliar.

Post by maurert »

If you hadn't said that you had other FTP clients upload at the 100KB/Second I'd have said that you were hitting the limit of your aDSL line. I peaked out at 45-48KB/Second, but 45-48 KileBytes is in the neighboorhood of 450-600 Kilobits/second of a most aDSL lines.

Todd
SFSW
Posts: 9
Joined: Sat Dec 09, 2006 5:49 pm

Post by SFSW »

I have a 1.5 Mbs DSL connection, so it's definately capable of speeds greater than 45K.
SFSW
Posts: 9
Joined: Sat Dec 09, 2006 5:49 pm

Post by SFSW »

Wow, that's a neat test! Anyway, my results were:

1291 kbps Download Speed
742 kbps Upload Speed
SFSW
Posts: 9
Joined: Sat Dec 09, 2006 5:49 pm

Post by SFSW »

Are you sure you weren't confusing download rates with upload rates? The 100-150 KB/s would be right in line on downloads for your connection.
Yup, quite sure. Like I mentioned earlier, sometimes the slowest speed is 75K (which is probably normal if my upload speed tests around 750 Mbps) for uploads. But I often get about 100-150K (this variation could be in the difference between uploading object code files vs ASCII files and/or connection quality at any given time). But it doesn't matter what I try to upload with CoreFTP, the speed never exceeds about 40-45K. Could it be something the FTP server is doing? Perhaps with the way CoreFTP is connecting to it vs how other FTP programs would connect to it?
Brendon K
Posts: 139
Joined: Mon Aug 15, 2005 8:16 pm

Post by Brendon K »

Out of curiosity, have you uploaded LARGE files for these tests? If you've only uploaded small files that upload pretty quickly, the average transfer rate could be calculated differently between FTP clients (although unlikely, but still possible). By large, I'm thinking about 30 MB files. Just make sure not to go crazy, we don't want you over-allocating your monthly bandwidth quota for tests. :)

Try uploading a rather large file with each of your tested FTP clients to see if the transfer rate averages out to the same speed, or if CoreFTP is still somewhat lacking.

Also, if you're not already using the v2.0 series, try using that, there have been some speed improvements. (I didn't see if you said you were using a specific version of CoreFTP...)

-- you might also want to grab a stopwatch and time these uploads as well, if CoreFTP is reporting the transfer rate incorrectly, that would be helpful to know too; just write down the file size of the test, the clocked speed (stopwatch) and the transfer time as reported by the software --

If you want to test this on someone else's server, let me know and I'll create a temporary FTP account on my server to let you test. I rarely use my site... :P
SFSW
Posts: 9
Joined: Sat Dec 09, 2006 5:49 pm

Post by SFSW »

Out of curiosity, have you uploaded LARGE files for these tests?
Yes, it's about the only way I can accurately gauge the performance comparision between the various FTP programs. Large file sizes range from about 9 MB up to about 25 MB.
Also, if you're not already using the v2.0 series, try using that, there have been some speed improvements. (I didn't see if you said you were using a specific version of CoreFTP...)
According to the opening window, I am using Version 1.3c build 1447.6. I have not tried the 2.0 build yet, it looks like that is a beta version?

EDIT: Just tried 2.0 build 1477, it also maxed out at 40K.
-- you might also want to grab a stopwatch and time these uploads as well, if CoreFTP is reporting the transfer rate incorrectly, that would be helpful to know too; just write down the file size of the test, the clocked speed (stopwatch) and the transfer time as reported by the software --
I have loosely clocked the transfers with the clock on the Windows taskbar and the software seems to be accurately reporting the time it takes, so it appears the upload speed really is limited to about 45K.
If you want to test this on someone else's server, let me know and I'll create a temporary FTP account on my server to let you test. I rarely use my site...
I'd be happy to try any further test.
Brendon K
Posts: 139
Joined: Mon Aug 15, 2005 8:16 pm

Post by Brendon K »

PM sent with further information.

CP: Does CoreFTP do any compression on the file transfer? I'm thinking perhaps the other clients do some sort of compression...just a thought.
SFSW
Posts: 9
Joined: Sat Dec 09, 2006 5:49 pm

Post by SFSW »

Thanks to Brendon K, I was able to run the test. The test confirms the problem is NOT with CoreFTP, I just got upload speeds at 75K with his server. So I will focus on what is wrong/different with the server I'm using and how it is working with CoreFTP vs other FTP programs.
SFSW
Posts: 9
Joined: Sat Dec 09, 2006 5:49 pm

Post by SFSW »

The only difference I can spot between the two connections is the use of SSL for the server I'm connecting to. Is there a default speed difference in using an SSL connection versus not using SSL?
tdi
Posts: 4
Joined: Sat Dec 11, 2004 6:29 pm

I got luck... i guess..

Post by tdi »

Hi.. greetings

I think i have some luck, as the configs of my web supplier...allows me to have sustaineable (able to mantain...?) 77k transfers.... the speakeasy.net test you commented above, rates my connection at 100/70 from -Texas, and little lower from other places, and from Washington nearly half of that. (I'm on México). So I guess the problem you have are local to your webhost..
mmmmh.. it's interesting... there must be some tweak that your sever needs...

Greetings

PS. i'm so newby... so I don't think i'm using SSL or other stuff. as the only parameters i put on the connection.. were host, username, password, and the rest I left alone... so... use that info...
Post Reply