Hi Jay,
I would talk to WPEngine about this. I know they have used P3 and are familiar with it. It may be a matter of temporarily disabling eaccelerator or some other extension for your site.
Hi Jay,
I just wanted to follow up. Did WPEngine get back in touch with you and get everything sorted out? Please let me know if you have any further questions.
Thread Starter
jaybna
(@jaybna)
We never got P3 to run but I did find a solution to track down slow queries. Thank you for following up! jay
Hi,
I had the same trouble with P3 and WP Engine. Quite a long time ago.
I had a discussion with Kurt, if I remember right, who correctly indicated that the plugin requires some sort of “higher level” access – I don’t remember exactly what it was that was needed – and that maybe I did not have that access at WP engine.
This was exactly the problem. So one of the support staff at WP Engine ran P3 for me, with the necessary access, it worked correctly.
I will try and see if I can find what was the issue.
In the mean time I’d be interested to know what other solution your found, jaybna, since I am still interested in tracking and resolving issues with poor response times.
Found it. In an old thread. Opcode optimser was the issue. See here:
http://wordpress.org/support/topic/does-not-recognise-other-plugins
One additional thing, jaybna:
The big resource drain on our site was identified by P3 as WPML (multilingual plugin).
Are you running a multilingual site with WPML?