PHP-FPM enabled by default on account creation

benny@cpanel.net ●

This is now public, and available in v66 in the CURRENT tier! Get a quick overview of all the improvements on the version 66 Release Site. If you have questions, feel free to join me for the next few hours in this public hipchat room:

https://www.hipchat.com/gQ7xUUD7i

1

Andrzej ●

I came here from a support request. Really surprised it's not possible to use FPM by default!

Reply URL

1

benny@cpanel.net ●

We've been discussing internally what it would take to get this request resolved. It's not officially on the roadmap yet, but it's definitely something we'd like to get added.

Reply URL

1

Petit Ours Blanc ●

I believe PHP-FPM should be the default configuration for all accounts in cPanel because it causes infinitely less load compared suPHP. and that means every cPanel machine that runs PHP will have just a fraction of its current load, saving cPanel's customers combined millions in hosting fees and enabling them to scale much easier.

suPHP on our server caused 5 times the load compared to PHP-FPM. PHP-FPM has all the security advantages of suPHP, combined with the raw speed of DSO. there is no major downside. everyone wins.

Reply URL

1

nrm ●

On my hosting statistic suPHP is a best choice for users by default (too many different cms/sites etc). How about easy modify and use many different php.ini files with PHP-FPM?

URL

1

Marcelo Pedra ●

Hello everybody. I would like to analyze and discuss the pros and cons of having PHP-FPM enabled for everyone in a shared server with 350 accounts and only 8 GB of RAM. The load, we know, will be kept at remarkably/unbelievable low values, but what about RAM usage? Is there any possibility that this feature become a resource hog?

And what could happen with resource usage when cPanel release FastCGI options?

Reply URL

2

Yuri ●

The RAM usage of FPM is similar to the old mod_fcgid.

The FPM Pool process tries to reuse the currently opened PHP process for that user, only opening new ones when it have concurrent requests.

When use SuPHP every php request create a new process without any reuse or speed or cpu optimization, wasting much more time, CPU and RAM.

When use mod_php (dso, with or without ruid2), most of the PHP engine is preloaded in apache main process, diminishing the RAM and CPU usage per PHP process, but in other hand it don't support any other apache MPM than prefork, so the apache will initiate a new process per request wasting much more RAM than any other way, and part of PHP engine is loaded in each apache child process, even for non-php content.

That's the why the FPM/FastCGI process are much more efficient, it's a surprise to see that it's don't enabled by default.

URL

1

Petit Ours Blanc ●

Hi Kent,

You're right to ask this. I think with the benefits of the increased performance, overall you could end up with both less load and perhaps the same level of RAM usage. I didn't experience any noticeable increase in RAM usage when switching to PHP-FPM. If needed you could decrease the size of your server's database caches (we kept ours the same size) and in the end you're performance would still be much, much better than before.

Alex

Reply URL

1

Dejan ●

PHP-FPM really bring great performance improvement, and about 5-6 times lower CPU usage, almost without changes in RAM usage.

There could be some RAM usage increase with lot of accounts, but that is why this feature should be implemented to allow us to configure this per hosting package or feature list, so that we can create hosting packages that will use PHP-FPM by default, and also have other packages that will use SuPHP or CGI or whatever is configured as default on the server.

Reply URL

3

benny@cpanel.net ●

This request has made it to one of our product backlogs! We may (and I stress MAY) be able to squeeze this into the development for version 64, but it's not for sure yet and there are many moving parts that could push it out further. As soon as I know anything for sure I'll let you know!

Reply URL

1

Micheal ●

Hi benny.

Is there an change in v64 on this feature?

Reply URL

1

benny@cpanel.net ●

There's no official word yet, but it looks like the work for this hasn't gotten started yet. Since we're just two weeks from the end of feature development for version 64, I'd say it's pretty unlikely. I'll update again once we hit the end of feature development.

URL

2

benny@cpanel.net ●

I just checked in with the team that had this on their backlog for version 64 and can confirm that this will not make it into version 64. It's on the list for discussion as we go into planning for version 66, but we don't have anything firm yet. As soon as I know more, I'll be back!

Reply URL

1

Micheal ●

Hi Benny;

We are ready to wait for v66.

This function is especially important for system administrators, and the sooner we will be, the happier we will be.

Good luck cpanel team. :)

Reply URL

4

benny@cpanel.net ●

This is on the list of goals for version 66! Once it gets developed and is available for public testing in an EDGE version I'll be back to let everyone know!

Reply URL

3

benny@cpanel.net ●

This is now in a public EDGE-tier build of cPanel & WHM:

* Implemented case CPANEL-13191: Allow setting PHP-FPM for new accounts by default.

* Implemented case CPANEL-13227: Enable PHP-FPM on all domains as they are created.

Please do take a look, if you have a server on the EDGE tier. Otherwise, look forward to it being included in version 66!

Reply URL

1

andrelop ●

Great news !

Do we have an ETA regarding version 66 ? Not exactly, just a tentative/aproximate date so we could decide if we go now for 64 or if we wait for 66, as this feature is important enough for us to maybe delay our new installs.

Regads,

URL

2

benny@cpanel.net ●

66 will go to the CURRENT tier sometime in late June or early July.

URL

1

Jason Jersey ●

This is awesome. Thank you!

URL

1

Hutina Teodor Silviu ●

Hi Benny,

This will also apply to Addons and Subdomains when they are created or just for the main domain ?

Reply URL

2

benny@cpanel.net ●

I don't know the answer to that question, but I will ask!

URL

1

Micheal ●

Hi all.

I tested it.

It works fine for subdomains, but the addon domains does not work.

URL

2

benny@cpanel.net ●

I just heard back from our developers: they should both work, however there's a bug with addon domains. We're taking a look, and by the time it goes to production it will support both.

URL

1

Greg ●

Great News ! Look forward to v66 - one question though, while being able to enable FPM by default can we also set default pool options so that we don't have to manually change each one? Or would this be an additional feature request?

Thanks

Reply URL

1

benny@cpanel.net ●

That would be an additional request, it looks like.

URL

1

Marcelo Pedra ●

@Greg: That's an interesting point. Let us know if you open it as a new request.

URL

2

John Hawkins ●

I believe it may already exist here: https://features.cpanel.net/topic/php-fpm-enhanced-configuration

URL

1

Greg ●

@Marcelo Sorry I haven't had time to do one - work has been real busy atm however I will happily up vote any related request. If the one John posted doesn't cover what we need

URL

2

Marcelo Pedra ●

@Greg + @John Hawkins : I think the thread linked by John is what we were talking about. Liked and following now.

Thanks John!

URL

1

Greg ●

@Marcelo I have just managed to have a read at the request and I agree that seems to cover what we are looking for Liked and following too !

@John thanks for sharing that link with us

URL

2

Micheal ●

Thank you, thank you, thank you, Benny and cpanel team.

I'll start testing.

Reply URL

2

benny@cpanel.net ● ●

This is now public, and available in v66 in the CURRENT tier! Get a quick overview of all the improvements on the version 66 Release Site. If you have questions, feel free to join me for the next few hours in this public hipchat room:

https://www.hipchat.com/gQ7xUUD7i

Reply URL

PHP-FPM enabled by default on account creation

Merged Objects

Make PHP-FPM or FCGI the default handler.

Replies (16)