Database issue!! ??

[wegoecono]

Hello, have a site that is getting flagged by the host for using too many resources. The database is huge ~200mb and I think it’s related to events calendar plugin! I did some checks and it seems this is a known issue? How can I confirm it’s caused by the plugin, and then how can I fix it? Site is not live now as it’s down so need options asap please! thanks!

[Jaime Marchwinski]

Hi Adam,

Thanks for reaching out!

I’d recommend taking a look at Our Favorite Developer Plugins, especially something like Query Monitor, which may be able to point you to where some of the issues are with your site.

In general, you might want to have a look at our Performance Considerations and see if there is anything you can adjust in order to help your site run better:

https://theeventscalendar.com/knowledgebase/performance-considerations/

After that, you may be interested in caching, so take a look at this article:  https://theeventscalendar.com/knowledgebase/caching-basics/

Let me know how it goes and if you need any further assistance on this topic!

 

Thanks,

Jaime

[wegoecono]

Thanks Jaime, but this didn’t quite answer the question. Let me know if I need to provide more details. Sadly I can’t access the backend of the site to get a report on the plugin, perhaps if the site is reinstated soon I can.

That said: did I not see that there was a problem with this plugin leaking into the db and causing a bloated issue and slowing sites down? I could have sworn I saw that in past threads.

Are there certain areas of the DB we can look (I have access to that) to see if this plugin is affecting it? Or a search to see if there are too many of a specific call (eg. lots of transients) that would tell us what is happening here?

Is there a specific “Events Calendar Plugin DB Cleanup” process or plugin to use?

We were told our public_html/index.php is the culprit of the resource hog – does that help at all?

If I could get the system info to share would that help? Is there a way to get that info w/o having access to the WP admin?

Please advise, thank you VERY MUCH!

[wegoecono]

More so confirmed, after having DB reviewed, it’s WAY big and we see lots of “_transient” entries. I believe this is related to the plugin. I will be sharing privately the system info next. Thanks.

[wegoecono]

This reply is private.

[Jaime Marchwinski]

Hi Adam,

Thanks for getting all of this information to me.

It seems that this is related to a known issue with transients.  In the meantime, if you do have access to your WordPress backend, there are a few plugin options that may help to clear out your transients.  Please keep in mind that these are third-party plugins, and we are not affiliated with them in any way.

You may want to check out Transients Manager and/or  WP-Sweep to help clear your transients.

We apologize for the inconvenience caused by this glitch and we are actively working on a solution for this.  I cannot guarantee when it will be fixed, as it’s in the development team’s hands now.  They need to assign it, code it, test it, and schedule it for release.  The good news is that you will be contacted as soon as a fix is available.

Thank you for your patience as we see this through and please let me know if you have any other questions in the meantime!

 

Thanks,

Jaime

[wegoecono]

Ah…. I knew I wasn’t crazy!

thank you for following up. I tried using those plugins and to be honest, because of just how many transient lines there were (and I mean, like 12K lines!!!) the plugins would choke. I found a code option to run in MySQL to clear them out so for the time being, I think it may be okay. But this is a BIG issue – it kicked 2 of my sites off line by the host who would NOT put them back until “something” was fixed – they didn’t say what it was but we found it.

I suspect many people have / will have this issue so I look forward to your fix. Thank you.

[Jaime Marchwinski]

Yes, this is definitely an issue that we have seen with other users and we are actively working on a fix for it.  Thank you for your patience throughout this process!

[Victor]

Hi Adam!

First, we wanted to apologize for the long delay in getting back to this topic in regards to the issue reported here.

We’ve reached to the conclusion that the lack of decent garbage collection (for transients stored in the database) is a general shortcoming that is best addressed from the WordPress core side of things.

We know some other plugins face with the same issue. The good thing is there are several great tools out there, such as the WP Transients Manager, that can solve this problem.

As a result, we don’t wish to duplicate efforts by baking in our own transient garbage collector if solid general purpose tools (like WP Transients Manager) already exist to do the same job.

As always, if you decide to implement one of these tools, we suggest to setup a dev/staging site so you can test things out without disrupting the live site.

Don’t hesitate to reach out to us for any follow up questions you may have.

Best,
Victor

[Support Droid]

Hey there! This thread has been pretty quiet for the last three weeks, so we’re going to go ahead and close it to avoid confusion with other topics. If you’re still looking for help with this, please do open a new thread, reference this one and we’d be more than happy to continue the conversation over there.

Thanks so much!
The Events Calendar Support Team

[Author]

Posts