Community
Participate
Working Groups
Hi, First I want to apologize very much!! for submit of this ticket, but it's just plain fact and reality. i tested the speed of the RSE FTP feature, i tested upload and i compared results with Aptana FTP feature and FileZilla upload speed. For my test I chose/selected to upload Zend Framework 1.9.4 library (only the library folder) through FTP protocol (not FTPS or SFTP), which have: Size - 20.7 MB folders - 407 files - 2335 My connection speed is: Download speed: 1 926,06 kbit/s (240,76 kB/s) Upload speend: 532,37 kbit/s ( 66,55 kB/s) Web Ping: 13.2ms (min) 21.3ms (average) 34.9m (max) Connection Stability: 87.2 % The results are horrible, the upload speed of the RSE FTP feature is very very slow. Upload speed test: FileZilla - 4 min. 47 sec. Aptana FTP - 17 min. 16 sec. RSE FTP - 37 min. 51 sec. So only one, what developers to do is optimize, optimize and again optimize, because Zend Framework isn't so big project, i'm developing projects, which have 3-5 times more files than Zend Framework and I know project which have 20 times more files than have Zend Framework and it's unimaginable to work with this project with the RSE FTP feature :( So the priority of this issue is for me critical and using RSE FTP feature is unusable for me :( I hope that in feature versions will be changes related to the speed and I hope that peoples will vote for this issue. Have i nice day. ;)
Hi dev, it's soon 3 months from post this problem. Not that you started to do something, but neither you have responded. So any response and any future planing how to solve this issue.
There's two issues that impact FTP performance: - bug 269171 excessive sending of NOP commands (fixed in 3.2m6) - bug 180965 single-threaded operation I'd appreciate if you could run the test again with RSE 3.2m6 wher ebug 269171 has been fixed. Also note that I have reduced severity to "enhancement" since functionality is OK now.
I know this is a really old ticket, but I'm seeing similar issues on RSE FTP 3.6.1 from Neon. The performance is slow but acceptable for smaller text files, but for large binary files it is unusable. I'd like to know where I can get started to track this down. Can anyone point me in the right direction?
(In reply to Cole Markham from comment #4) Hi Cole, As a first step I suggest you measure the scenario that you are interested in, and compare with other FTP clients like the original submitter did. This bug originally talked about uploading folders with lots of files - is that what you care for, or uploading one single large file ? Second, FTP is not a very efficient transport mechanism; Git, Rsync or dstore deal with the transport stream in a more efficient way as they can compress data on the fly. And SSH has a more efficient implementation in RSE than FTP (it can leverage a pool of multiple streams whereas FTP is single-threaded as per bug 180965). Once you know more clearly where you want to get to, it should be easier to give proper advice on how to debug and improve RSE.
