On Jan 4, 10:27 am, "alex.gay...@gmail.com" <alex.gay...@gmail.com> wrote: > Ok, but you're original concern was that what happens if say you go to > send an email and "raises the issue that e-mail may take a while (i.e. > from a few seconds to a couple of minutes) to send;", ultimately if > you join on that thread than you've reduce the overhead insofar as the > new length of the request is now length(sending the email) - amount of > the time the rest of the stuff you do before you join() takes, but if > it's taking 30 seconds to send the email, you're still ultimately > going to be taking a minimum of 30 seconds to serve that request.
That's true, but then if e-mail is taking 30s to send you're probably going to need to fix that as a bottleneck; this might be a nice solution to a problem, but it won't be able to fix *everything*. Not to mention that if it's taking 30s for 1 email, a batch system is going to take aaaaages to flush the e-mail queue. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
