[FQuest Announcement] PHP7 Now available

[Bruce]

Originally Posted by mromero

For those of us that upgraded to PHP 7 a couple of days ago do we need to go in and re-upgrade or is it now done automagically by FQuest?

There is no need to do anything, just an indication that the specific version numbers were bumped.

To be more specific, there is only one version of the PHP 7.2 series installed, and one of the 7.3 series. When we upgrade, every site on each version will run the upgraded version with no intervention required.

Preliminary tests show NO PERFORMANCE BOOST upgrading my sites to PHP 7.

Originally Posted by phppete

Hi,

What is the req/sec compared to your previous php 5.x apache module?
Will we see a performance boost or will there be more sites per server therefore no noticeable difference?

Thank you

[Bruce]

Originally Posted by mromero

Preliminary tests show NO PERFORMANCE BOOST upgrading my sites to PHP 7.

We have been tracking a problem that is causing PHP 7 to crash when the opcache is enabled. The only fix we have at the moment is to disable opcache which, of course, will have a negative impact on performance for some scripts.

[Bruce]

Originally Posted by phppete

What is the req/sec compared to your previous php 5.x apache module?
Will we see a performance boost or will there be more sites per server therefore no noticeable difference?

I have no information right now about performance differences. As the PHP module is now running as a separate process from the web server, there is some overhead involved in communicating the request and response between processes. However, PHP 7 also brings advances in execution performance. As indicated in the previous message, we are also dealing with a crash bug (that didn't appear until the right combination of software was running) that requires that we turn off opcache for stability. Which of these effects is dominant, I cannot say.

The primary motivation to the different PHP mode is ease of integration with the web server and ease of future upgrades. It should also help provide extra information when scripts cause loading issues and provides an extra security barrier between the web server and running scripts. We do not expect it to allow for more accounts on the servers in the short term at least.

Good job. I was for a moment thinking Fquest was cramming more sites rather than speeding up individual web sites with PHP 7 and looking forward hopefully HTTP/2 and a later version of MYSQL.

[phppete]

It would be good to have OpCache working, especially on a shared hosting environment. Response times can be 50% faster, overall speed 14% increase.

Do you know when this issue will be resolved?

Originally Posted by Bruce

I have no information right now about performance differences. As the PHP module is now running as a separate process from the web server, there is some overhead involved in communicating the request and response between processes. However, PHP 7 also brings advances in execution performance. As indicated in the previous message, we are also dealing with a crash bug (that didn't appear until the right combination of software was running) that requires that we turn off opcache for stability. Which of these effects is dominant, I cannot say.

The primary motivation to the different PHP mode is ease of integration with the web server and ease of future upgrades. It should also help provide extra information when scripts cause loading issues and provides an extra security barrier between the web server and running scripts. We do not expect it to allow for more accounts on the servers in the short term at least.

[voiceguy]

FWIW I upgraded two different Wordpress installation to 7.3.11 and all seems to be working fine. These are both light on plug-ins.

VG