New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Confirmation emails can take a while to get sent #1118

Closed
henare opened this Issue Mar 7, 2017 · 2 comments

Comments

Projects
None yet
1 participant
@henare
Member

henare commented Mar 7, 2017

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.

@henare

This comment has been minimized.

Show comment
Hide comment
@henare

henare Mar 7, 2017

Member

Instead of doing the smart thing I just did the dumb thing and observed this happening by sending emails to myself. I've observed that it can take a couple of minutes to process a batch of alerts and that confirmation emails are stuck in the queue behind them.

Member

henare commented Mar 7, 2017

Instead of doing the smart thing I just did the dumb thing and observed this happening by sending emails to myself. I've observed that it can take a couple of minutes to process a batch of alerts and that confirmation emails are stuck in the queue behind them.

@henare henare self-assigned this Mar 7, 2017

@henare henare changed the title from How long does it take for confirmation emails to be sent? to Confirmation emails can take a while to get sent Mar 7, 2017

@henare

This comment has been minimized.

Show comment
Hide comment
@henare

henare Mar 7, 2017

Member

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?

Member

henare commented Mar 7, 2017

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?

@henare henare closed this in 5413429 Mar 7, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment