Indeed, the high load is caused by php-fpm. I was wondering if there was
any alternative config to keep fpm from spiking (like, any built-in
to pass the final location without any plugin…).
I will look into the compiled module. I’m not very comfortable with
compiling it on the cluster of servers which were previously using
but it’s better than nothing (uh, tips to keep the debian specific
structure when compiling?).
Thanks for pointing me out!
---------- Forwarded message ----------
From: Cliff W. [email protected]
Date: Wed, Feb 29, 2012 at 9:35 PM
Subject: Re: Uploads with nginx 1.0.12
To: [email protected]
On Wed, 2012-02-29 at 20:59 +0100, Adrián Navarro wrote:
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
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).
Here’s some references: