thanks
Terry
]]>Sometimes we have tens of thousands of entries that we would like to export, but the problem is that we have to increase the server timeout limit to an unreasonable amount, which takes considerable server resources. Is there a plan to improve the plugin so that it can process all the entries more effectively? For example, processing entries in batches so that the server receives some response and doesn’t time out and also the export process would require much less memory.
Thank you!
]]>Hi,
After updating Mailpoet to v.3.73.0 (on 5th November), there has been a spike in CPU use on my hosting server (Siteground), from an average of 20,000 secs/day to over 180,000 secs/day of CPU usage.
I opened a ticket with Siteground and the technical support found a spike in calls to the following:
- public_html/index.php
- public_html/wp-cron.php
- public_html/wp-admin/admin-ajax.php
After some troubleshooting, I’ve isolated the cause: if I disable Mailpoet the CPU usage goes down to normal but as soon as I enable Mailpoet the CPU usage on the server goes up again.
Is this a known issue? Do you have any suggestions to try and solve the problem, without having to downgrade the plugin to a previous release?
Thanks,
MG
]]>I installed this plugin and everything was fine (23000 redirects).
However, due to traffic increasing, my hosting provider put Mysql in other Serve2.
Since that day the plugin take down my server when is activated.
I deleted the plugin and tables, then I installed again…however the issue occurs again (It take all Ram 28 GB in 1/2 minutes)
I Find this error on debug.log
[14-May-2021 18:31:12 UTC] PHP Fatal error: Maximum execution time of 600 seconds exceeded in /home/xxxx/public_html/wp-content/plugins/404-solution/includes/PermalinkCache.php on line 198
Can you help me?
]]>Thanks
]]>The site has been running since 2005 and is fairly popular, and we’re now finding that we’re struggling for server resources and sometimes get out of memory errors. I’ve done the usual tweaks (caching with w3 total cache, cloudflare, an increased memory allowance, removing a couple of theme customisations that were running uncached queries), but it’s a small charity without much budget. Searches across 11,652 Posts are taxing our resources.
I could trim the older posts, but I’m concerned that if I do that, I will then get a pile of 404 traffic for those old posts, and I don’t think 404s can be cached either, so that will make the problem worse not better.
What can I do to make best use of our limited server resources so that users can still run searches and access other uncached content?
]]>