mpakier
Member
Hello
I started using the plugin and it's great.
When the list of recipients was about 700 it was working fine.
The I added longer list (more then 4000) and it is hardly working.
I disabled wp-cron and added it to crontab on my server
but it did't helped too much.
So my question is if there is a way to send all the newsletters
at one in bulk, as a script on the server or some other way?
mpakier
Member
After few days of trying different settings I had to kill the queue. Sending more then 4000 is simply not working (it is sending about 10 /hour). So I made few newsletters with 700 recipients in each and now it works fine.
I think that the problem may be with database structure or queries. With 4000 in a queue it becomes extremly slow. I had few times to restart the database because it was unresponsive long time.
alo
Key Master
Hi. Thanks for report. I'd like to have feedbacks from other people that have 4000+ recipients, to understand if it is a common issue.
Anyway, when you open the thickbox to create the list of recipients, you can click the "send now" button to send newsletter immediately to all recipients, without using cron.
About cron queue, you can increase the cut-off of emails you can send per batch and per day. More info about cron: http://www.eventualo.net/blog/wp-alo-easymail-newsletter-faq/#faq-8
I hope it helps.
mpakier
Member
Hello. I checked your code and I think I know where is a problem.
Look at the function alo_em_get_recipients_in_queue. It creates
a list of emails to send one batch of newsletter. The SQL inside is
something like this:
SELECT<br />
r.*, s.lang, s.unikey, s.name, u.ID as user_id, s.ID AS subscriber<br />
FROM<br />
wp_easymail_recipients AS r<br />
LEFT JOIN wp_easymail_subscribers AS s ON r.email = s.email<br />
LEFT JOIN wp_users AS u ON r.email = u.user_email<br />
INNER JOIN wp_postmeta AS pm ON pm.post_id = r.newsletter<br />
INNER JOIN wp_posts AS p ON p.ID = r.newsletter </p>
<p>WHERE<br />
pm.meta_key = '_easymail_status' AND pm.meta_value = 'sendable' AND r.result = 0 AND p.post_status = 'publish' AND newsletter = 1306<br />
ORDER BY r.ID ASC LIMIT 100There is a lot of joins here. The problem is that there is no index on wp_users.user_email so the joins
can't be optimised by database. I have 6000 records in wp_easymail_recipients, 6000 in wp_easymail_subscribers and 15000 in wp_users. This select takes for me 2,5 minutes
Then for every newsletter email that you send you run alo_em_get_recipients_in_queue
with the same joins. When the batch is 100 it takes 250 minutes to run this selects.
So wp_cron runst every 10 minutes a send batch that takes 250 minutes. This is why
it was not working at all and why it killed my database.
If you fine tune this SQL the script will work probably 100 times faster. The major problem
is removing the join with wp_users. You use it only to take wp_users.ID. This is the variable
that never change so you can copy it to wp_easymail_subscribers.
alo
Key Master
Thanks for the precious remarks and benchmarks.
Ok, I'll remove the join to wp_users table and I'll add a new user_id column in wp_easymail_recipients.
Then... what about the join to wp_easymail_subscribers? Instead of the join, I could add 3 columns (s.lang, s.unikey, s.name) in wp_easymail_recipients. Infact these 3 values usually never change. What do you think about this opportunity? Does it make the query significantly faster in your opinion?
alo
Key Master
I fixed it in v.2.2.1. Many thanks again for your help.
You must log in to post.
