Apache + virtual hosts + php-fpm?

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Apache + virtual hosts + php-fpm?

Rose, John B
Looking at the php-fpm homepage …


it says this …

It was not designed with virtual hosting in mind (large amounts of pools) however it can be adapted for any usage model.

Are folks using Apache with numerous virtual hosts, still using mod_php as the preferred approach? With I assume prefork MPM?



Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Apache + virtual hosts + php-fpm?

Eric Covener
On Wed, Aug 2, 2017 at 9:12 AM, Rose, John B <[hidden email]> wrote:

> Looking at the php-fpm homepage …
>
> https://php-fpm.org
>
> it says this …
>
> It was not designed with virtual hosting in mind (large amounts of pools)
> however it can be adapted for any usage model.
>
> Are folks using Apache with numerous virtual hosts, still using mod_php as
> the preferred approach? With I assume prefork MPM?

I can only assume they mean "hundreds of users with their own pools in
one fpm daemon" as you might find on shared hosting / mass hosting.

Most people on php-fpm will have moved on to event. Once the PHP
interpreter outside of the server, there's no reason to stay on
prefork.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Apache + virtual hosts + php-fpm?

Daniel
If you pay attention to everything in that page seems totally outdated.

Better check: http://php.net/manual/en/install.fpm.php

or this:

http://php.net/manual/en/book.fpm.php


No matter how you look at it, except for a very knowledgeable few,
mod_php just confuses the hell of a lot of people.

Moving to fpm helps people:

* Allow the use of event in httpd, using the best scaling mpm there is
for httpd.
* Discern where their real problems are when there are slowdowns.
* Better choice for configurations through different pools in FPM.
* Can even separate Apache from PHP execution in different boxes to
distribute load accordingly, cheaper boxes can be used for httpd, and
probably heavier processing ones for PHP with fpm.
etc etc..


2017-08-02 15:23 GMT+02:00 Eric Covener <[hidden email]>:

> On Wed, Aug 2, 2017 at 9:12 AM, Rose, John B <[hidden email]> wrote:
>> Looking at the php-fpm homepage …
>>
>> https://php-fpm.org
>>
>> it says this …
>>
>> It was not designed with virtual hosting in mind (large amounts of pools)
>> however it can be adapted for any usage model.
>>
>> Are folks using Apache with numerous virtual hosts, still using mod_php as
>> the preferred approach? With I assume prefork MPM?
>
> I can only assume they mean "hundreds of users with their own pools in
> one fpm daemon" as you might find on shared hosting / mass hosting.
>
> Most people on php-fpm will have moved on to event. Once the PHP
> interpreter outside of the server, there's no reason to stay on
> prefork.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>



--
Daniel Ferradal
IT Specialist

email         dferradal at gmail.com
linkedin     es.linkedin.com/in/danielferradal

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Loading...