Posted: December 2, 2015 at 2:50 pm
|
|
Hello, We are having some performance issues on our WP4.3.1 site on Page.ly managed hosting and their support staff is pointing the finger at Event Espresso 3.1.37.3.P as one of the performance sucking culprit plugins as follows: ************* PAGE.LY: You have all this list of cookies and php sessions causing the site to bypass our cache: Set-Cookie: mc_session_ids[default]=c4b3be0813867994039dd6c7eac26b21b84bd138; expires=Wed, 02-Dec-2015 20:32:39 GMT; Max-Age=300; path=/; domain=.co medyguys.com; secure; httponly These are most likely from plugins, unfortunately you have many plugins that you’re going to have to sift through to pinpoint the session_start() function. ******************************* ME: I understand that we have a lot of plugins active and most are the same ones we have been using without issue since moving to Page.ly, but the performance issue (30 second page loads) is very recent. Perhaps an update changed something and I need to isolate that. Can you provide any insight into what type of plugin or feature might employ the session_start()function ? Any info that might help me narrow the search? ******************************* PAGE.LY: It looks like these are the relevant ones. wp-content/plugins/event-espresso/espresso.php: session_start(); There are more but those appear to be in some Disabled directories. *********************************** My questions to Event Espresso Support Staff are: We are only using one gateway (AuthNet), so can we safely remove all the other directories to placate Page.ly and eliminate them as something they can point to as robbing performance? Should inactive gateways matter at all? Is this something other event Espresso clients experience related to poor performance? Please advise. Thanks |
An inactive gateway’s code is not executed. So they would only affect things if they were actually activated. What’s interesting is, the one instance of session start they mentioned from the WorldPay gateway is commented out. That means the session start will not execute even if WorldPay is activated. I’m afraid that removing the inactive gateways’ code will likely not help matters since Pagely support, even if they do more than a cursory glance of the code, will still see that espresso.php uses the session_start() function. While Event Espresso does use sessions though its registration process, you might consider upgrading to EE4 as it tends to be more performant.
This is the first time I’ve see a report from a host that claims Event Espresso’s use of session_start() is the cause of poor performance. |
|
The support post ‘Page.ly Hates Disabled Gateways’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.
