Database Optimisation
R
Recyclart
You should really optimize how you save the email sending queue in the table _mailpoet_sending_queue.
On my websites, for the bigger one, this table is several Go and continues to increase with time... until the server crash.
Why are you saving each email in plain HTML in the database? You should save only one version of the global email and then optimize to call this email for each user... not save each email in the table, I have dozen of thousands of the same emails in my table...
Really, they're a lot of improvements to be done here! It's ok for small websites but for bigger ones it's not really possible.
Franz Neumeier
I know people who have switched to other newsletter sending providers for this very reason. And statistics are not that important for everyone, so there should at least be an option to delete older data.
Martijn Joosse
I also need this, my sending_queues table is over 1 GB, and keeps growing, with over 22.000 subscribers. There should be some options to manage this, for example choosing to delete the old data, by year/month. The same for the statistics tables.
Ján Mikláš
Merged in a post:
House Keeping - reduce old database entries
S
Sebastian
MailPoet so far has no mechanism at all to clean old database entries.
Eg statistics and tasks.
With high volume newsletter sending this fills up the database and the server storage fast.
Our backup broke through too huge database tables. Other effects might be the need to upgrade DB and slow down speed.
Statistics could be compressed to end results.
Tasks should be just cleared from the DB after a short while.
L
Laurent Matignon
Upvoted. Should be the top priority.
On one of my websites the wp_mailpoet_scheduled_task_subscribers
table has ~7 352 370 lines!
It has a big impact on my website performance.
Major issue here.
Simon Whyatt
Yes, the database needs to be much leaner. Most of my WordPress sites have a total combined database of under 100MB, whereas the mailpoet sending queue table alone in a site with >5000 subscribers and only a handful of mails sent is already over 100MB! Even a database heavy WooCommerce site with 100s of products and users typically doesn't exceed 800MB in total. My hosting has a database limit of 1024MB per website. That's typically 10+ times larger than necessary but now looks like it might be insuficient for a site using MailPoet.
Luc NAROLLES (Surligneur de Talents !)
Hello
I strongly encourage you for this work, especially given the number of tables
Thanks
Alexander B Kerekes
Good idea! I've upvoted it. Would you mind taking a look at my feature request for a Campaign tab and consider upvoting it, as well?
Thanks!
Borja Odriozola
I'm facing the same problem too. I hope the Mailpoet team solves it soon, otherwise my clients and I will most likely turn to another service.
Kirsch
Bien sûr !
welsstreams
Agree. When considering use of Mailpoet, offline storage as an option for this content would be better. Provide an option to delete after X days.
Load More
→