Hi All -
Just looking for some tips & tricks or advice, experiences, opinions... on tuning the GlobalScape SFTP Server for optimal upload performance when using SSL over
FTP. Our SSL is a signed certificate from Thwate as opposed to a self-signed key created in GlobalScape.
I recognize that upload speed will be determined by the ISP limitations of the user doing the uploads, but I want to ensure the highest possible throughput to the server from the client. I haven't done much yet in terms of setting Max. Transfer Rate in the GlobalScape software itself.
Personally, my ADSL line can sustain around 35KB/sec of upload speed to the server hosting GlobalScape in our environment. This is from my apartment to our servers, all within the same country (only about 20km away from the servers). And 35KB/sec is what I get to other FTP sites I've tried, so no problem there.
But once in a while users will complain about very slow upload speeds, and when I look in the Server stats in the Admin. page of GlobalScape in real-time, can see their upload speed is like 6KB/sec and I even saw one guy uploading at 2Bps. I can't verify it, but these users tell me they have regular ADSL lines and theoretically they should be hitting 35KB/sec also. I have noticed a few times, when connecting to GlobalScape using the cmd prompt in Windows, that doing ftp> dir will load 1 character at a time; e.g. if the file name is test_upload.txt, then the letter "t" appears, then .5 sec later the letter "e" appears, then .5 seconds later the letter "S" appears ... normally doing ftp> dir spits out the entire directory structure in .5 seconds - but once in a while I'll do this crazy one-letter-every-half-seco
nd stint.
So I'm looking for advice or tips on how to ensure that the SSL over FTP uploads from any client will be limited only by the upload speeds of their ADSL line as opposed to a limitation on our GlobalScape settings or configuration. Or pretty much any tips on performance tuning a GlobalScape FTP server.
Thanks,
NDB
Start Free Trial