Sendy sending at a crawl
@Ben,
Since 1.1.3 rolled out and I upgraded, my sending went from about 750 sends per minute on average to about 50! Its super slow and I think it has something to do with the queue addition in the DB -- i see I have a bloated queue table in the DB at about 500MB and growing! I am hitting 100% max utilization on an EC2 Large instance which shouldn't happen. Any advice?
Since 1.1.3 rolled out and I upgraded, my sending went from about 750 sends per minute on average to about 50! Its super slow and I think it has something to do with the queue addition in the DB -- i see I have a bloated queue table in the DB at about 500MB and growing! I am hitting 100% max utilization on an EC2 Large instance which shouldn't happen. Any advice?
This discussion has been closed.
Comments
Previously, each row is deleted after the email has been sent to them. How it works now is that the row won't be deleted even after an email is sent. Its
sentstatus will be marked as1instead. Only after all emails are sent will the whole queue table be emptied.I just pushed out a new update (version 1.1.3.1) where the
query_strcolumn that holds the huge query string per row will be emptied after each email is sent so that your database size will be reduced dramatically when sending. Sending speed also increased by 4 times when I tested. http://sendy.co/get-updated