Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am trying to write a simple, in-house file delivery application for uploading files for easy download on our client’s end. I am using Flash with a very basic PHP script receiving the file. So far, this does work.
The problem statement is: using FTP, a 100 MB file will upload in 2-3 minutes. Using my simple Flash uploader and uploading to the same destination, it takes 3-5x longer. Is there any way I can adjust my PHP/Apache settings to improve upload time?
I can’t imagine that much of an overhead with a Flash upload component.
Can you, as Xeoncross has already recommended, use a different one just to make sure it’s nothing program specific? SWFUpload‘s standard example should be quite easy to set up.
Then, is there any post-processing happening on the server and that might prolong the request? What happens if you let the receiving script die() right away, is the time difference still that much?
How (with what hostname/IP) are you addressing the FTP server, and how does the browser address the script that parses the upload?
I don’t think there is anything you can do on the PHP end of things, because the PHP script only comes into play when the file has been fully uploaded. The only thing there could be a web server misconfiguration – Apache or whatever you’re running – but this is a very remote possibility.