News for hackers. Stuff that matters.

A comment on 10 000 concurrent real-time connections to Django. Parent comment

Re:10 000 concurrent real-time connections to Django by stefantalpalaru on Wednesday March 27, 2013 @07:46AM (#5448798)
It's not PostgreSQL's fault that Django closes the connection after each request explicitly (see close_connection() for what was done before 1.6):

[1] https://github.com/django/django/blob/master/django/db/__ini...

[ Parent | on HN ]
Re:10 000 concurrent real-time connections to Django by raverbashing on Wednesday March 27, 2013 @09:57AM (#5449377)
I understand that, and I'm not saying that there aren't several issues in Django (but some are getting better)

What I'm saying is that with PgBouncer you have Django <> PgBouncer <> Postgresql, right?

So what PgBouncer is doing (dealing with several open/close connections) maybe could be done better inside PostgreSQL

[ Parent | on HN ]