On Wed, Dec 9, 2009 at 11:50 PM, David Koblas <kob...@extra.com> wrote: > I'm trying to get a better understanding of django performance in a > production setting. > > Specifically I've seen notes that say that operations like sending mail will > block all production traffic to your server for the duration of the send. > That got me thinking about other backend calls, like sending email call > external URLs etc?
That's a bit of a simplistic analysis, and it's only completely true if your production web server can only accept a single connection - something that isn't true of any real production web server (or just about any web server *other* than Django's development server). The issue here is the resources that are being consumed to serve a request, and the time at which they are released. When a client connects to a web server, they consume one of the available threads/processes that the server uses to satisfy clients. That specific thread or process will not be able to serve other clients - i.e., it will be blocked - until it returns a response. It doesn't matter what you do to construct the response - call a database, send mail, or calculate Pi to 10000 decimal places - until the response is returned the thread/process won't be released. Then you then need to deal with contention *between* threads/processes. For example, if your mail server can only accept a single connection at a time, having 10 webserver threads simultaneously try to send mail will cause slowdown in each of those threads. > Is this right, or is there some magic that makes MySQL "better" than just a > urllib call. In short, this is correct. There isn't any magic difference between urllib vs mysql vs email in terms of raw server performance. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
