-
Notifications
You must be signed in to change notification settings - Fork 331
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
php 5.6 performance issues #139
Comments
can you elaborate? what sort of performance issue? memory usage? cpu? during build? application runtime? has it gone up from previous versions of the 5.6 image? how does it compare with the same metrics for the 5.5 image? |
Sorry edited my initial message just as you replied. Applications running with 5.6 are significantly slower to respond which often leads to 504 responses It's not a resource issue as metrics do not report any limits being reached |
Can you define significantly? does this apply to trivial(hello world) apps? Have you done any profiling to see where the time is being spent? |
The current issue is reported based on prod running apps like WordPress and
Laravel, returning the 504 timeout.
Switching to 5.5 and 7.0 resulted in massive improvements. Eg. One WP site
used to take 10+ seconds to render after receiving 2 simultaneous users.
Now it's almost under a second.
Im investigating further now. Will report back with other findings.
…On Tue., 20 Dec. 2016, 1:03 pm Ben Parees, ***@***.***> wrote:
Can you define significantly? does this apply to trivial(hello world)
apps? Have you done any profiling to see where the time is being spent?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#139 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACItsFS3RKu6Jz9CzD9sAxiEntl1GLjJks5rJzd6gaJpZM4LRSv8>
.
|
Here is just some basic tests a customer ran, this seems to run slower across all the PHP images (in comparison to local PHP and an OpenShift 2 cluster): time php test.php
php-56-centos7:
php-70-centos7:
php 5.4 (openshift 2):
PHP 7.0 (centos 7 own docker image):
The different versions make it a bit hard to do comparisons but it's obviously noticeable that the S2I images are effecting performance. I ran these tests on the exact same hardware configuration. |
can you share the dockerfile for the php7-centos image you built? I take it you're just running "docker run -it sometime /bin/sh" and then running your time php operation? |
The php7-centos image uses Remi's RPMs rather than the SCL https://raw.githubusercontent.com/andrewklau/docker-centos-lamp/master/Dockerfile The S2I images were tested with both |
@andrewklau Do you also see performance differences between different php56 images, like whether it can be caused by changes in the latest build? |
@remicollet FYI |
PHP 7.0 is much faster, and use less memory than PHP 5.6, this is expected. this is even one of the most important PHP 7 change. |
@hhorak this has happened for quite some time (a few months) @remicollet yeah, however 5.5 seems to perform better than 5.6 |
Here's another test, using the exact same deploymentconfig
centos-lamp (php 7.0 remi)
php-56-centos7
|
Please compare enabled extensions (output of php -m) E.g. some extensions, like XDebug could have performance impact. |
Ah!! Sorry the above results were centos-lamp and php-56-centos7 I believe PHP55 does not have XDebug enabled I believe this would be related to #122 |
PHP 55/70
PHP 56
Only php56 has xdebug being explicitly installed. |
I have a similar problem with 55 and 56 performance cpu |
We have been receiving increased reports for performance issues with the 5.6 image.
5.6 has issues with slow response times which often leads to gateway timeouts etc.
Downgrading/upgrading to 5.5/7.0 resolve the problem.
The text was updated successfully, but these errors were encountered: