| From | Sent On | Attachments |
|---|---|---|
| Adrián Navarro | Feb 29, 2012 11:58 am | |
| Cliff Wells | Feb 29, 2012 12:35 pm | |
| Adrián Navarro | Feb 29, 2012 12:48 pm | |
| Cliff Wells | Feb 29, 2012 1:30 pm | |
| Valentin V. Bartenev | Feb 29, 2012 1:41 pm |
| Subject: | Re: Uploads with nginx 1.0.12 | |
|---|---|---|
| From: | Valentin V. Bartenev (ne...@vbart.ru) | |
| Date: | Feb 29, 2012 1:41:33 pm | |
| List: | ru.sysoev.nginx | |
On Thursday 01 March 2012 00:35:51 Cliff Wells wrote:
On Wed, 2012-02-29 at 20:59 +0100, Adrián Navarro wrote:
Hello,
I am using file uploads with nginx 1.0.12, php5-fpm and php 5.3.10.
Currently, big file uploads (~1300 MB) do take about 30 seconds to process after the file is being uploaded, and the CPU load spikes. Is there a way to prevent that?
I assume that since the spike occurs *after* the upload, the culprit is PHP, not Nginx?
I am using a very simple script (just a var_dump($_FILES), nothing more,
Assuming the spike is caused by PHP, you might take a look at the nginx_upload module, which will handle the entire upload process for you, and just hand your PHP script a path to the uploaded file (along with a few other parameters).
Actually,
fastcgi_pass_request_body off; client_body_in_file_only clean; fastcgi_param REQUEST_BODY_FILE $request_body_file;
should do approximately the same.
wbr, Valentin V. Bartenev
_______________________________________________ nginx mailing list ngi...@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx





