News for hackers. Stuff that matters.
Re:Fixing Database Connections in Django by hcarvalhoalves on Friday March 08, 2013 @05:23PM (#5346140)
Appended to my comment:

> You'll have a different pool per worker process, and they won't persist when you restart your workers - right when you need low latency the most

Re:Fixing Database Connections in Django by zzzeek on Friday March 08, 2013 @06:05PM (#5346351)
So, pooling that has TCP/DB initialize connect overhead during a restart only is "worse than" having TCP/DB initialize connect overhead on restart as well as every subsequent request ?

There's pros/cons to in-app pooling vs. middleware pooling, but calling in-app pooling "worse" than no pooling at all is kind of misleading.

If I were using PGBouncer, I'd probably leave SQLA's pooling on anyway, so at least you have no TCP latency at all on connect. unless you're dealing with apps that go unevenly idle/active.

Re:Fixing Database Connections in Django by hcarvalhoalves on Friday March 08, 2013 @06:25PM (#5346438)
> but calling in-app pooling "worse" than no pooling

You don't need to get all worked up. Nowhere I affirm it's worse than no polling.

I'm talking about not reinventing the wheel, specially since pooling inside the worker is inferior than just setting up pgpool.

Re:Fixing Database Connections in Django by zzzeek on Friday March 08, 2013 @06:28PM (#5346451)
there's a lot of cases where just running an app and having it talk to the database in a halfway-efficient way is a lot more convenient than having to install and start a whole separate service.

As well as, in-app pooling is the easiest way to limit the max simultaneous connection checkouts per application. If PGBouncer were to handle this, I'd assume you'd need to either send distinct usernames or some other instance-specific token over so that it could identify sources of connections.