New Relic has been disabled on the VIP Go platform since October 19th due to performance issues. This post is to provide another progress update, and some good news.
Investigation Update
As noted in our last update, we’ve been experimenting with various configuration options, and features disabled, and measuring impact to response times and error rates. We discovered that the overhead from the New Relic agent was greatly reduced with framework-specific options disabled, including the WordPress specific functionality.
The performance cost of enabling New Relic is now in the expected range of 10-12%, and we’re confident that this won’t cause instability on customer sites.
Next Steps
We can now safely re-enable New Relic more widely, including to non-production sites on request. Please open a support ticket if you’d like New Relic re-enabled on any of your VIP Go sites, and we’ll be happy to assist.
Our team is continuing to work with New Relic engineers on improvements to the New Relic agent that may allow us to re-enable the framework-specific functionality without additional overhead. We’ll post another update on that, along with a longer term plan on New Relic configuration options for VIP Go sites going forward.
Thanks for your continued patience, and please reach out if you have any questions.
WordPress VIP Lobby 