I have a general doubt about file uploading or downloading on server. When we are using filezila or cuteftp for upload or download website then it works very fast. and we can transfer any type of file but same file when we upload through any website then
it is very slow . if website is running from same server . and our internet speed also constant then where is the diffrence ?
FTP and HTTP downloads provide different methods for sending files. FTP is going to always be better for larger files because of its low overhead, however HTTP provides some conveniences, especially when downloading lots of smaller files it permits some
ability for concurrency performance enhancements among other things.
As far as ASP.NET goes you have access to both the HttpWebRequest/Response and FtpWebRequest/Response objects to upload/download using FTP or HTTP so the choice is ultimately yours. For speed performance and throttling you are going to need to configure
IIS appropriately though. Which settings of course depends on your setup. I have several Silverlight multi uploaders that use HTTP to upload mass files and because the files are expected to be smaller I throttle the speed lower to make for better over all
performance for all users.
When you use an FTP program such as CuteFTP or FileZilla, you are using just that, FTP. The program is designed to manage all over head for any and all FTP transfers you have and improve performance as much as possible because you are a single user. This
is not the same when it comes to IIS, IIS is meant to be a server hosting for hundreds if not THOUSANDS of users from your endpoint(s).
That means if i want to provide faster uploading or downloading then i should use FtpWebRequest/Response objects ?
I understand that FTP users are less then website users . But if we take an ideal condition that only 1 user have using FTP and only 1 user have using HTTP . Then , will both performance same ? and if not then why ?
Honestly I would say unless your system meets certain conditions, and unless you are going to have at least 100 simultaneous downloaders/uploaders then you won't notice much of a difference. You may either use a web service / Wcf Service or some other method
for providing uploads/downloads but if you are wanting the ASPX page to do it then you are going to be using the FTP or HTTP resquest/response methods yes.
Check out the following link for some more detailed info on FTP vs HTTP
shwetamber
Participant
1252 Points
294 Posts
My curiosity
Feb 21, 2012 07:32 AM|LINK
Hello,
I have a general doubt about file uploading or downloading on server. When we are using filezila or cuteftp for upload or download website then it works very fast. and we can transfer any type of file but same file when we upload through any website then it is very slow . if website is running from same server . and our internet speed also constant then where is the diffrence ?
Thanks & Regards
Shwetamber
N_EvilScott
Star
8179 Points
1466 Posts
Re: My curiosity
Feb 21, 2012 07:41 AM|LINK
FTP and HTTP downloads provide different methods for sending files. FTP is going to always be better for larger files because of its low overhead, however HTTP provides some conveniences, especially when downloading lots of smaller files it permits some ability for concurrency performance enhancements among other things.
As far as ASP.NET goes you have access to both the HttpWebRequest/Response and FtpWebRequest/Response objects to upload/download using FTP or HTTP so the choice is ultimately yours. For speed performance and throttling you are going to need to configure IIS appropriately though. Which settings of course depends on your setup. I have several Silverlight multi uploaders that use HTTP to upload mass files and because the files are expected to be smaller I throttle the speed lower to make for better over all performance for all users.
When you use an FTP program such as CuteFTP or FileZilla, you are using just that, FTP. The program is designed to manage all over head for any and all FTP transfers you have and improve performance as much as possible because you are a single user. This is not the same when it comes to IIS, IIS is meant to be a server hosting for hundreds if not THOUSANDS of users from your endpoint(s).
shwetamber
Participant
1252 Points
294 Posts
Re: My curiosity
Feb 21, 2012 08:03 AM|LINK
Hi,
That means if i want to provide faster uploading or downloading then i should use FtpWebRequest/Response objects ?
I understand that FTP users are less then website users . But if we take an ideal condition that only 1 user have using FTP and only 1 user have using HTTP . Then , will both performance same ? and if not then why ?
Thanks & Regards
Shwetamber
N_EvilScott
Star
8179 Points
1466 Posts
Re: My curiosity
Feb 21, 2012 08:22 AM|LINK
Honestly I would say unless your system meets certain conditions, and unless you are going to have at least 100 simultaneous downloaders/uploaders then you won't notice much of a difference. You may either use a web service / Wcf Service or some other method for providing uploads/downloads but if you are wanting the ASPX page to do it then you are going to be using the FTP or HTTP resquest/response methods yes.
Check out the following link for some more detailed info on FTP vs HTTP
http://daniel.haxx.se/docs/ftp-vs-http.html