|
pniekamp
|
July 16, 2015 at 2:53 pm
Over the weekend, our WordPress website has slowed to a crawl. I’ve cleaned the database, updated all the plugins, and run Plugin Performance Profiler. The issue seems to point the Event Espresso’s core, which is using nearly 78% of the load time. We’re experiencing significant mysql activity on the options table. I erased 21K transient vars today.
I don’t want to ditch EE, but I’m not finding any solutions to this issue. Does anyone have any advice?
Info:
WordPress Version:
4.2.2
PHP Version:
5.3.29
MySQL Version:
5.1.73
Event Espresso Version:
4.7.8.p
Addons:
EE_Calendar
|
|
Lorenzo Orlando Caum
|
July 17, 2015 at 11:52 am
Hi Patricia, could you share feedback on these questions?
1. Could you please share an example of the transient key for transients that was cleaned out (all Event Espresso transients are prefixed with ee_)?
2. Is wp-cron disabled?
Thanks
|
|
pniekamp
|
July 17, 2015 at 3:47 pm
Hi Lorenzo,
Thanks for responding quickly. We’re running out of time on this.
1. 611 new transients have been created since my post yesterday. Here are a few (removed table name for security):
SELECT option_value FROM **_options WHERE option_name = ‘_transient_timeout_ee_ssn_bd9f3503f0ec21abd1a669e1dad964c0’ LIMIT 1
SELECT autoload FROM **_options WHERE option_name = ‘_transient_ee_ssn_bd9f3503f0ec21abd1a669e1dad964c0’
SELECT autoload FROM **_options WHERE option_name = ‘_transient_timeout_ee_ssn_bd9f3503f0ec21abd1a669e1dad964c0’
SELECT option_value FROM **_options WHERE option_name = ‘_transient_timeout_doing_cron’ LIMIT 1
2. WP Cron is not disabled. Should I disable it and try to run the cron job manually?
|
|
Josh
|
July 20, 2015 at 10:27 am
No, you should not disable WP Cron. The cron job will automatically run to clean up the expired transients when they’re due to expire, as long as it’s not disabled or there’s another plugin that’s disabling it. Can you monitor the options table to make sure the expired transients do get deleted?
611 transients in 24 hours would be normal if you’re getting about 300 registration form submissions per day (there are two transients per transaction).
|
|
pniekamp
|
July 21, 2015 at 11:46 am
Thanks Josh. We aren’t getting nearly that many registrations a day. I’ve been monitoring the table and manually deleting the transients, however, I’m not seeing a performance boost. The only significant performance boost I’ve seen is deactivating EE. I’d really rather not move to another plugin because we’ve invested a significant amount of work and time in EE and haven’t experienced issues yet. Is there anything else you can think of that we should review?
|
|
Josh
|
July 21, 2015 at 12:24 pm
One thing that could create additional load is if a lot of the registration form or ticket selection form submissions are coming from bots. To prevent this, you can try installing a plugin like Block Bad Queries. You can also check the EE transaction logs for more information about what’s hitting the ticket selector/reg form pages (eg. it may help to ban an IP address if it’s hitting the server continuously).
|
