PHP-FPM and nginx tweaks - My server is OOMing (so it seems)

You've got it set to run up to 60 copies of PHP… I'm not convinced that there's any benefit in running more than 8 to 12 in the typical case, possibly going a bit beyond that. Remember, you only have four processor cores, and those processors can only do one thing at a time; having a few extra PHP processes can be good if you're blocked on something like I/O or network stuff, but 60 seems grossly excessive.

What size is your linode and what software are you running anything memory intensive (lots of wordpres/drupal plugins, image processing etc)?

Depending on your linode size I'd say pm.maxchildren = 60 is high pm.startservers = 20 is high … pm.minspareservers = 5 is high… pm.max_requests = 500 is probably low

Also consider using a unix socket instead of binding to a port, they're a bit faster.

@obs:

What size is your linode and what software are you running anything memory intensive (lots of wordpres/drupal plugins, image processing etc)?

Depending on your linode size I'd say pm.maxchildren = 60 is high pm.startservers = 20 is high … pm.minspareservers = 5 is high… pm.max_requests = 500 is probably low

Also consider using a unix socket instead of binding to a port, they're a bit faster.

I'm running just one web app that evolves a lot of image resizing. It's a kind of heavy application and it runs on a 1024 Linode.

I'll try the socket instead of the port and reduce pm values. Any tips on what should I use instead?

And should I use pm.max_requests = 0? Or increase the number is a better approach?

Thanks guys!

I'd go for pm.max_children = 6 pm.start_servers = 2 pm.min_spare_servers = 2
This will allow 6 processes to use 75% of your system resources assuming each process uses at most 128mb ram. This is pretty conservative I doubt your image processing will use that much ram but better safe than sorry.

Keep an eye on it and increase the pm.max_children by 1 until you're happy you're using the right amount of ram.

pm.max_requests is used to kill a process after it's run X amount of requests, good for dealing with memory leaks you can set it to 0 and see if your system stays stable if it doesn't then set it to say 5000 and keep an eye on it dropping it if you still have problems.

Thanks for the tips!

I tried this config but after an hour or so I started getting the 504 error again. This time I think the VM wasn't OOMing. I was monitoring it closely.

I've increased pm.max_children = 10 and let's see what happens. Any other tips?

Anything in your nginx/php error logs?

Here is the tail of my php-fpm.log as soon as I got a new 504:

> Jul 15 14:51:28.178668 [NOTICE] Terminating …

Jul 15 14:51:28.191899 [NOTICE] exiting, bye-bye!

Jul 15 14:51:28.269103 [NOTICE] configuration file /etc/php5/fpm/main.conf test is successful

Jul 15 14:51:28.327797 [NOTICE] fpm is running, pid 2112

Jul 15 14:51:28.331697 [NOTICE] ready to handle connections

Jul 15 14:51:32.333643 [WARNING] [pool www] seems busy (you may need to increase startservers, or min/maxspare_servers), spawning 8 children, there are 0 idle, and 7 total children

Jul 15 14:51:33.334597 [WARNING] [pool www] seems busy (you may need to increase startservers, or min/maxspare_servers), spawning 16 children, there are 0 idle, and 9 total children

Jul 15 14:51:34.334975 [WARNING] [pool www] seems busy (you may need to increase startservers, or min/maxspare_servers), spawning 32 children, there are 0 idle, and 11 total children

Jul 15 14:51:46.343101 [WARNING] [pool www] server reached max_children setting (20), consider raising it

Thanks for the help guys :)

Guys,

I reallly need some help here! Nothing is working… I've upgraded my linode to a 2048, increased the number of processes and I keep getting errors…

My traffic has grown A LOT these late days and I really need some help here. I'm kind of freaking out. Anything would help. Thanks!

PHP-FPM is still under development only just got the experimental flag removed. You could compile snapshot version (5.3 or 5.4) from http://snaps.php.net/ and see if the problem still exists.