Home › Forums › Newsletter Plugin Support › Speed results using Amazon SES plugin & SES API. Any way to increase the speed?
- This topic has 4 replies, 2 voices, and was last updated 7 years, 4 months ago by Mohib.
January 29, 2016 at 1:49 am #20333
I’m running on BlueHost shared, and also tested using a local install of WordPress on my fast Windows 7 computer as a baseline for comparison.
wp-cron.php was set to start every 5 mins.
“Max emails per hour” was set to 12,000 so it runs every 5 mins or 1,000 per 5 min block.
Connection to Amazon was via the SES API not SMTP.
Test of 4 messages to a list of 500 test email addresses — continuous 2,000 emails totals.
Best speed reached — local or on Bluehost: average of only 100-110 per minute (500-550 per 5 minute block).
Using other native Windows emailing software (not The Newsletter Plugin) connected to Amazon via the SES API (not SMTP) also on the same computer, I’m able to send about 1,200 emails a minute — about 10 times faster.
Bluehost does not indicate it had to perform any CPU throttling, and of course on the local install there was no sharing or other issues, but it was the same speed as the shared blue host.
Any suggestions on how to increase the speed 4 or 5 times? I would like to get upto at least 400-500 per minute.
ThanksJanuary 29, 2016 at 6:11 am #20338
I was looking at this information here, https://www.thenewsletterplugin.com/plugins/newsletter/newsletter-configuration#advanced
PHP max execution time
Sending newsletters can be a slow process, it depends on the speed of the mail service. External SMTPs can be much slower than the standard method of sending emails from PHP.
PHP has a maximum execution time that, if exceeded, force the PHP engine to kill the process. Sending many emails can take longer than allowed.
Newsletter has an internal protection to avoid that and stops the delivery on a single batch if the maximum allowed time is reached. So, if you set an engine speed of 1200 emails per hour, hence 100 emails per batch, you can experience a lower number of emails sent per run. It’s due to that protection.
If you are confident enough to increase the maximum execution time of PHP, you can force the value (in seconds) using this configuration. Be aware: PHP running in safe mode will ignore this setting. To know the actual PHP preset value, see the system values on the diagnostic panel.
It says “To know the actual PHP preset value, see the system values on the diagnostic panel” and I checked the diagnostics and both my bluehost and local versions say:
PHP Execution Time 0 (seconds)
I don’t understand what 0 seconds means.
Can I increase the email speed if I enter something in “PHP max execution time” on “Advanced settings”? If so what kind of numbers should I try to see the difference?
ThxJanuary 30, 2016 at 1:51 pm #20395StefanoKeymaster
Zero means no limit, so it’s already ok. A native software can be far more optimized and specially it can be mutithread, feature not supported by PHP (we are working a simulation for it)January 30, 2016 at 6:12 pm #20403
Ok great. Yes you are right regarding multi-thread but am very pleased you’re working on a way to simulate that for TNP. Any idea when that might be ready because that would certainly put TNP in a whole new class of delivery capacity compared to all the other WordPress newsletter plugins.February 7, 2016 at 11:26 pm #20539
Any idea on when the multi-threaded delivery engine may be available?
- You must be logged in to reply to this topic.