Please share your agent version and other relevant versions below:
NR PHP Agent 22.214.171.124, PHP version 7.0.27
Please share your question/describe your issue below. Include any screenshots that may help us understand your question:
We run a fleet of Amazon Linux servers in AWS, on the m4.large instance type. Our applications run in docker (ECS) using the official php-apache image from docker.
We recently upgraded to the latest Amazon Linux AMI (ECS-Optimized) that included the patches for the Meltdown vulnerability. After doing this, we saw a 2x-6x response time penalty in most of our web applications. It seems like the most impacted applications are the ones that run on top of larger frameworks (primarily Zend Framework 1, Zend Framework 2, and Doctrine 1). The application that was affected the most (going from about 250ms average response time to over 1500ms) actually loads both Zend Framework 1 AND Zend Framework 2.
Two of our web applications that don’t load any of these large frameworks seem to be impacted very minimally.
We found two solutions to fixing this problem (other than the obvious, rolling back to the previous AMI build), both of which appear to get us back to the pre-upgrade response times:
- Upgrade to m5.large (I assume this is due to newer CPUs being able to perform a more efficient Meltdown mitigation)
- Remove the New Relic PHP Agent
Option #1 isn’t a viable option for us currently because of the reservations that we have locked in with AWS. However, after some digging, it turned out that the New Relic PHP Agent was the main culprit behind our response time increase, when running on m4.large instances. I just wanted to report our findings with this, and see if anyone else had experienced similar issues.