Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Confirmation emails can take a while to get sent #1118
When you create an alert or make a comment you have to confirm it over email so it's important that these are sent very quickly.
I'm asking this question because I think these kinds of mails are sent using the same queue that processes alert emails. Does this mean that if a batch of alert emails takes a few minutes to send that these emails are queued waiting to send? That would not be a good user experience and it would be a pretty easy fix to create another queue or something.
Wow, I'm surprised this hasn't been more of a problem. Because the number of alert subscribers has been steadily growing we're now sending batches of 100 every 2 minutes. I observed batches taking about 2 minutes to send, which means confirmation emails had to slip into spots between batches running.
We can alleviate this by creating a dedicated worker for the confirmation messages so they're sent to Cuttlefish quick-smart.
However if we're only able to send 100 messages every 2 minutes and we have a new batch every 2 minutes then that means we won't be able to get all our batches processed in a day. It's easy enough to add another worker but is Cuttlefish the bottleneck?