Slow Sending – Big batch at beginning, than 1 mail / 10 minutes

Looking at the log it seems there are problems with transients. Do you have an object caching plugin?

Hi Stefano, thank you for your fast reply! Actually there is no cachingplugin installed. As we are building a new webseite for this customer and didn’t build the current site, I didn’t update the plugins and wordpress to not break something. Could this be a bug of the old pluginversion 7.5.1? After the sending is finished I could update it, but it was working before, so I think this might not be the solution. Do you have any other hints? ??

Kind regards

Hi, that “blocked by transient” is a protection we have to avoid concurrent runs of the delivery engine. When a batch is completed, the transient is removed “unlocked” the next batch execution. I suspect the transient is still there and it lost the “timeout”. I see sometimes this problem on some blogs.

I use the plugin “transients manager”. Install it and check if there are transients named newsletter_* without a timeout.

Hi Stefano,

this is what I got.

Kind regards

That’s the problem, delete the _engine transient.

Hi Stefano,
I already did it but it didn’t help. It recreates an entry everytime the service ran which sets a timeout for around 5 minutes. The sendspeed and the logs didn’t change except the processed user ID.
Kind regards

Maybe something with those settings?

The 5 minutes timeout is correct, the engine runs every five minutes.

Hi Stefano, thank you, but as I’ve written it didn’t help. ?? I guess the problem is, that the batch size is so small. The first batch is arround 80 and than it’s lowered to 1 even if it says Loaded subscribers: 82.

29-06-2023 06:15:42 ... Newsletter::send> Query: select * from wp_newsletter where status='C' and id>309 order by id limit 82
29-06-2023 06:15:42 ... Newsletter::send> Loaded subscribers: 82
29-06-2023 06:15:42 ... Newsletter::send> Batch size: 1

• This reply was modified 1 year, 5 months ago by haeki1.

Hi, the batch size is correct, don’t worry about that, it is for the turbo send of some delivery addon. The loaded subscriber count is what matter.

Ok, but regarding the status bar of the newsletter and regarding the logs of the smtp-plugin it’s sending only one mail in each batch loop, even ist loaded subs is 82.

Ok, check for fatal errors in your server error logs, it seems the loop ends prematurely. I’ve seen that problem with email addresses formally correct by some rules but incorrect by some other validators. Check the subscriber with email ID 310, maybe it has two dots in the address or an ending dot in the “name” part, before the @.

Hi Stefano, the error logs where a good hint, thank you! ?? It wasn’t the emails, it was the memory limit. I raised it to 256 and now it works. Is the middle part (48,0 MB/128 MB) of the newsletterlogs not the memory usage?

7.5.1 - 48,0 MB/128 MB - [cron]

[29-Jun-2023 10:05:07 UTC] PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /www/htdocs/xxasda/xyy/wp-includes/wp-db.php on line 2056
[29-Jun-2023 10:05:07 UTC] PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 32768 bytes) in /tmp/asdasdasd on line 1
[29-Jun-2023 10:05:07 UTC] PHP Fatal error:  Unknown: Cannot use output buffering in output buffering display handlers in Unknown on line 0

Yes, it is the memory usage as we get it from PHP. It’s rather weird a consumption of 48M while sending! Check the newsletter’s log now if you can see the deep step in memory consumption. 82 subscribers even wil all the profile fields filled up should not consume so much!

Hi Stefano, yeah, I thought so too. ??

It now even got up to 182M

29-06-2023 10:15:16 - DEBUG - 7.5.1 - 50,2 MB/256 MB - [cron] > Newsletter::send> Query: select * from wp_newsletter where status='C' and id>351 order by id limit 83
29-06-2023 10:15:16 - DEBUG - 7.5.1 - 51,0 MB/256 MB - [cron] > Newsletter::send> Loaded subscribers: 83
29-06-2023 10:15:16 - DEBUG - 7.5.1 - 51,0 MB/256 MB - [cron] > Newsletter::send> Batch size: 1
29-06-2023 10:15:16 - DEBUG - 7.5.1 - 51,0 MB/256 MB - [cron] > Newsletter::send> Processing user ID: 352
29-06-2023 10:15:16 - DEBUG - 7.5.1 - 51,0 MB/256 MB - [cron] > insert into wp_newsletter_sent (user_id, email_id, time, status, error) values (352, 240, 1688033716, 0, '') on duplicate key update time=1688033716, status=0, error=''
29-06-2023 10:15:17 - DEBUG - 7.5.1 - 182,7 MB/256 MB - [cron] > Newsletter::send> Processing user ID: 353
29-06-2023 10:15:17 - DEBUG - 7.5.1 - 182,8 MB/256 MB - [cron] > insert into wp_newsletter_sent (user_id, email_id, time, status, error) values (353, 240, 1688033717, 0, '') on duplicate key update time=1688033717, status=0, error=''
29-06-2023 10:15:17 - DEBUG - 7.5.1 - 124,9 MB/256 MB - [cron] > Newsletter::send> Processing user ID: 354
29-06-2023 10:15:17 - DEBUG - 7.5.1 - 124,9 MB/256 MB - [cron] > insert into wp_newsletter_sent (user_id, email_id, time, status, error) values (354, 240, 1688033717, 0, '') on duplicate key update time=1688033717, status=0, error=''
29-06-2023 10:15:17 - DEBUG - 7.5.1 - 125,0 MB/256 MB - [cron] > Newsletter::send> Processing user ID: 356
29-06-2023 10:15:17 - DEBUG - 7.5.1 - 125,0 MB/256 MB - [cron] > insert into wp_newsletter_sent (user_id, email_id, time, status, error) values (356, 240, 1688033717, 0, '') on duplicate key update time=1688033717, status=0, error=''
29-06-2023 10:15:18 - DEBUG - 7.5.1 - 125,1 MB/256 MB - [cron] > Newsletter::send> Processing user ID: 357
29-06-2023 10:15:18 - DEBUG - 7.5.1 - 125,1 MB/256 MB - [cron] > insert into wp_newsletter_sent (user_id, email_id, time, status, error) values (357, 240, 1688033718, 0, '') on duplicate key update time=1688033718, status=0, error=''
29-06-2023 10:15:18 - DEBUG - 7.5.1 - 125,1 MB/256 MB - [cron] > Newsletter::send> Processing user ID: 358
29-06-2023 10:15:18 - DEBUG - 7.5.1 - 125,2 MB/256 MB - [cron] > insert into wp_newsletter_sent (user_id, email_id, time, status, error) values (358, 240, 1688033718, 0, '') on duplicate key update time=1688033718, status=0, error=''

• This reply was modified 1 year, 5 months ago by haeki1.