Am Freitag, 21. Juli 2017 19:55:17 UTC+2 schrieb Fred Stluka: > > Answer: Connection pooling > > Sharing a single DB user for all/multiple Web app users allows > connection pooling. Otherwise, you have to create a new DB > connection for each HTTP request, or at least for each web app > user. Creating DB connections is relatively slow. > > At least, I learned this reason 20 years ago, and assume it is > still true. On the other hand, I've never checked to see whether > Django uses a connection pool by default, and it seems pretty > quick. > > Does Django use a connection pool? > > >
I don't know if django uses a connection pool. I think not by default. The wsgi-workers handle one request after the other. I think this makes the thing fast. At least no complete db connection needs to be established for every request. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/23244090-aad8-4125-a121-d38cee28430b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
