Welcome! Log In Create A New Profile

Advanced

PHP-FPM pool management (1 per server or 1 per site)

Posted by Oleksandr Drach 
Oleksandr Drach
PHP-FPM pool management (1 per server or 1 per site)
August 02, 2013 11:36AM
Dear Community,

We want to host multiple highly-loaded websites (our own) on a webserver
with Linux+Nginx+PHP-FPM.
What is the best approach for pool management - create single pool for all
sites or create one pool per one site?

If I understood correctly in first case (single pool) if some site causes
issues to PHP then all sites will be affected.
In second case (poll per site) will we have greater memory/CPU usage?

Thanks in advance!

--

---
You received this message because you are subscribed to the Google Groups "highload-php-en" group.
To unsubscribe from this group and stop receiving emails from it, send an email to highload-php-en+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: PHP-FPM pool management (1 per server or 1 per site)
August 02, 2013 01:20PM
We prefer one pool per site. It allows you to use the chroot features per
site, and add a small, but extra layer of separation.

You can also change pool sizes per site, so if one site has more traffic,
you could give it more workers, and the others less.


On Fri, Aug 2, 2013 at 10:19 AM, Oleksandr Drach <luckyredhot@gmail.com>wrote:

> Dear Community,
>
> We want to host multiple highly-loaded websites (our own) on a webserver
> with Linux+Nginx+PHP-FPM.
> What is the best approach for pool management - create single pool for all
> sites or create one pool per one site?
>
> If I understood correctly in first case (single pool) if some site causes
> issues to PHP then all sites will be affected.
> In second case (poll per site) will we have greater memory/CPU usage?
>
> Thanks in advance!
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "highload-php-en" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to highload-php-en+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>



--
Vid Luther
CEO and Founder
ZippyKid
Managed Wordpress Hosting
http://zippykid.com/
210-789-0369

--

---
You received this message because you are subscribed to the Google Groups "highload-php-en" group.
To unsubscribe from this group and stop receiving emails from it, send an email to highload-php-en+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Joel Wallis
Re: PHP-FPM pool management (1 per server or 1 per site)
August 03, 2013 11:56AM
I think the multiple pools can be better, since you can configure PHP
differently for each site. Also, a good reason to do that is to separate
the log files site's problems and solutions. So, if something goes wrong
with one site, you'll need to fix it exacly in the respective pool.


Em sexta-feira, 2 de agosto de 2013 12h19min06s UTC-3, Oleksandr Drach
escreveu:
>
> Dear Community,
>
> We want to host multiple highly-loaded websites (our own) on a webserver
> with Linux+Nginx+PHP-FPM.
> What is the best approach for pool management - create single pool for all
> sites or create one pool per one site?
>
> If I understood correctly in first case (single pool) if some site causes
> issues to PHP then all sites will be affected.
> In second case (poll per site) will we have greater memory/CPU usage?
>
> Thanks in advance!
>

--

---
You received this message because you are subscribed to the Google Groups "highload-php-en" group.
To unsubscribe from this group and stop receiving emails from it, send an email to highload-php-en+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Oleksandr Drach
Re: PHP-FPM pool management (1 per server or 1 per site)
August 04, 2013 03:14PM
What about stability and resources utilization for different scenarios?

Пʼятниця, 2 серпня 2013 р. 18:19:06 UTC+3 користувач Oleksandr Drach
написав:
>
> Dear Community,
>
> We want to host multiple highly-loaded websites (our own) on a webserver
> with Linux+Nginx+PHP-FPM.
> What is the best approach for pool management - create single pool for all
> sites or create one pool per one site?
>
> If I understood correctly in first case (single pool) if some site causes
> issues to PHP then all sites will be affected.
> In second case (poll per site) will we have greater memory/CPU usage?
>
> Thanks in advance!
>

--

---
You received this message because you are subscribed to the Google Groups "highload-php-en" group.
To unsubscribe from this group and stop receiving emails from it, send an email to highload-php-en+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 56
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready