Portal Engine Questions on portal engine and web parts.
Version 6.x > Portal Engine > Send queued e-mails: is it one batch (e.g. 50) per run? View modes: 
User avatar
Member
Member
laurence-ecentricarts - 6/18/2013 1:54:01 PM
   
Send queued e-mails: is it one batch (e.g. 50) per run?
I would like to know how long it will take to send a Newsletter to a large number of Subscribers.

The static Newsletter is configured with "Send issues via e-mail queue" checked. The "Send queued e-mails" scheduled task is set to run every 1 minutes. The System E-mails setting for Batch size = 50.

Does this mean that a Newsletter mailing to 80,000 Subscribers should take 1600 minutes (80,000 / 50 or approx 27 hours) to be sent out?

Another view of the question: does the Execute(TaskInfo) method in CMS.Scheduler.QueueSender send a number of mails equal to the configured batch size, once each time it is called?

-- Laurence

User avatar
Kentico Customer Success
Kentico Customer Success
kentico_martind2 - 6/19/2013 6:34:20 AM
   
RE:Send queued e-mails: is it one batch (e.g. 50) per run?
Hi Laurence,

Yes, your deductions are right, but it also depends on the performance of your SMTP Server and if all the e-mails will be sent-out successfully.

And to the Execute(TaskInfo) method... if you will search for this method in the API reference, you will find out that it Sends all emails in a queue.

Best regards,
Martin Danko

User avatar
Member
Member
laurence-ecentricarts - 6/19/2013 7:31:33 AM
   
RE:Send queued e-mails: is it one batch (e.g. 50) per run?
Thanks for the reply, Martin.

The API reference indeed says that Execute(TaskInfo) sends all mails, and does not mention the batch size, so I am still not 100% clear.

Are you saying that the first time the scheduled task runs, it starts processing the mail queue of rendered Newsletter emails and it will process the entire queue even if the scheduled task does not run again?

The difference is: if the connection is good and the SMTP server is efficient, the 80,000 emails might get sent in much less time than 27 hours, since it will not wait for the next invocation of the scheduled task to send the next 50 mails.

Of course, real-world performance will depend on many other factors, but I am investigating just how things work at the Kentico side right now.

Cheers!
-- Laurence