Is the twentyZen working out of the box with a consumer-service daemon for the consuming command, or do I have to adapt something like the last line in the script:
COMMAND_QUEUE=“messenger:consume email --limit=$EMAILS_PER_BATCH --time-limit=$QUEUE_TIME_LIMIT|true”
Having a sending rate of 50 emails per second, It should be okay to change
EMAILS_PER_BATCH=14 to 50
and ignore the following values:
Email settings (Batch size needs to be adjusted to your mail service, if you send without queue)
The whole concept is based on cron jobs triggering the script. It reads the .env file and loops through all activated commands. E-Mail handling is a special loop, as it loops as long as there are mails in the queue up to the max.
You may look into timing. I loop through it by batches and adds the defined delay. Actually in the example it adds 1 sec in each loop to make sure its really not sending more than batch size in a second. This might be inefficient, if sending 50 mails already takes more than a second with this looping script. Delay could then be 0.
Thats why it always may need some adjustment.
Next level could really be to adjust it to a running daemon that sends continuously. I just don’t know the implications and how to control the speed of sending of the daemon.