Re: Database connection closed after each request?

Hi Mike, I tried with custom persistent connection, but results in same error. My environment is Django + postgres + nginx + gunicorn On Saturday, August 29, 2009 at 5:38:58 PM UTC+5:30, Mike wrote: > > Hi, > > I made some small custom psycopg2 backend that implements persistent > connection

Re: Database connection closed after each request?

Django-orm looks very useful. Any high DB traffic site using it in production? How mature is it? On Jan 15, 12:06 pm, Daniel Gerzo wrote: > On 15.1.2012 3:36, ydjango wrote: > > > Any updates on MySQL connection pool for django. Has anyone > > implemented it yet and willing to

Re: Database connection closed after each request?

On 15.1.2012 3:36, ydjango wrote: Any updates on MySQL connection pool for django. Has anyone implemented it yet and willing to share? Graham Dumpleton also raised it in G+ today. On Nov 20 2011, 5:45 am, Jonathan wrote: Does anyone know if this progressed anywhere

Re: Database connection closed after each request?

I've heard/read that MySQL proxy supports a connection pool. See (http://forge.mysql.com/wiki/MySQL_Proxy_FAQ) Basically this was a good original observation about the overhead of opening/closing DB connections for every request. I think tools exist out there such as MySQL proxy that can

Re: Database connection closed after each request?

I haven't used it, but this might help http://node.to/wordpress/2010/02/11/database-connection-pool-solution-for-django-mysql/Also, have you tried using SQLAlchemy? On Sun, Jan 15, 2012 at 8:06 AM, ydjango wrote: > Any updates on MySQL connection pool for django. Has

Re: Database connection closed after each request?

Any updates on MySQL connection pool for django. Has anyone implemented it yet and willing to share? Graham Dumpleton also raised it in G+ today. On Nov 20 2011, 5:45 am, Jonathan wrote: > Does anyone know if this progressed anywhere since '09? -- You received this

Re: Database connection closed after each request?

Does anyone know if this progressed anywhere since '09? -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/0fmsTMQC_tAJ. To post to this group, send email to

Re: Database connection closed after each request?

Just to throw my two cents in. My background is high-traffic fantasy sports websites (a different sort of geekness) and I've dealt with connection pooling and connection persistence separately on other ancient platforms. I will +1 Alex's observation that connection pooling and persistent

Re: Database connection closed after each request?

On Aug 31, 8:47 pm, Mike wrote: > Hi, > > I also would like to note that this code is not threadsafe - you can't > use it with python threads because of unexpectable results, in case of > mod_wsgi please use prefork daemon mode with threads=1 Provided you set

Re: Database connection closed after each request?

Hi, I also would like to note that this code is not threadsafe - you can't use it with python threads because of unexpectable results, in case of mod_wsgi please use prefork daemon mode with threads=1 --~--~-~--~~~---~--~~ You received this message because you

Re: Database connection closed after each request?

Hi, I made some small custom psycopg2 backend that implements persistent connection using global variable. With this I was able to improve the amount of requests per second from 350 to 1600 (on very simple page with few selects) Just save it in the file called base.py in any directory (e.g.

Re: Database connection closed after each request?

On Sun, Jul 26, 2009 at 10:17 PM, Amitay Dobo wrote: > So to sum up: I vote up connection pooling. Where do I sign up? Thread hijacking. Thanks, always appreciated. -- Glenn Maynard --~--~-~--~~~---~--~~ You received this message because you

Re: Database connection closed after each request?

On Sun, Jul 26, 2009 at 9:17 PM, Amitay Dobo wrote: > So to sum up: I vote up connection pooling. Where do I sign up? On some other project's mailing list? Connection pooling doesn't belong in Django. I've outlined one reason for that above. Google a bit for things like

Re: Database connection closed after each request?

I was quite surprised to find out there isn't any connection pooling built in to Django or (at least some of) its DB beack-ends when I've first researched about it. Other people have correctly pointed out that this is a latency issue that affects both low and high traffic sites. Since there is

Re: Database connection closed after each request?

On Fri, Jul 24, 2009 at 9:02 PM, Glenn Maynard wrote: > By the way, I switched my connections from TCP to a Unix socket with > local authentication and it dropped to 5-10ms.  (I suspect it was If you're using a connection pooler, you don't want to disconnect and reconnect from it

Re: Database connection closed after each request?

On Fri, Jul 24, 2009 at 9:20 PM, James Bennett wrote: > Suppose we start with a patch which does the sort of thing you > apparently want: hold on to the connection, and reset it after each > request/response cycle. That patch would never get committed, because > it would

Re: Database connection closed after each request?

On Jul 24, 8:54 pm, Alex Gaynor wrote: > "Seen under this light, the additional 150ms latency resulting from non- > persistent DB connection is huge - it implies almost 30% fewer > customer orders. And it has nothing to do with traffic." > > I'd just like to take a moment

Re: Database connection closed after each request?

On Fri, Jul 24, 2009 at 7:55 PM, Glenn Maynard wrote: > There are lots of requests for ways to build specific types of > queries, too.  You can't really commit a QuerySet method for one thing > and then... So, let's walk through this logically. Suppose we start with a patch

Re: Database connection closed after each request?

On Fri, Jul 24, 2009 at 8:36 PM, Andy wrote: > Seen under this light, the additional 150ms latency resulting from non- > persistent DB connection is huge - it implies almost 30% fewer > customer orders. And it has nothing to do with traffic. By the way, I switched my

Re: Database connection closed after each request?

On Fri, Jul 24, 2009 at 8:17 PM, James Bennett wrote: > While the specific thing you personally are asking for might not be > that much, we can't really commit it to Django and then say "Hey, we > only did this for Glenn and nobody else gets to ask for features > building

Re: Database connection closed after each request?

On Fri, Jul 24, 2009 at 8:36 PM, Andy wrote: > > On Jul 24, 4:39 pm, James Bennett wrote: >> Except this is what it turns into. So suppose a patch is added which >> does nothing except keep the database connection open; well, that's >> problematic

Re: Database connection closed after each request?

On Jul 23, 10:50 pm, Glenn Maynard wrote: > In this case, that's a terrible-performance-by-default approach. > (It's also not a default, but the only behavior, but I'll probably > submit a patch to add a setting for this if I don't hit any major > problems.) Agreed. Please

Re: Database connection closed after each request?

On Jul 24, 4:39 pm, James Bennett wrote: > Except this is what it turns into. So suppose a patch is added which > does nothing except keep the database connection open; well, that's > problematic because it means a server process/thread that's not > handling a request at

Re: Database connection closed after each request?

On Fri, Jul 24, 2009 at 7:03 PM, Glenn Maynard wrote: > What I need is sensible, simple and faster, but since someone else > might want to turn it into something complex and unnecessary, it > shouldn't be done? While the specific thing you personally are asking for might not be

Re: Database connection closed after each request?

On Fri, Jul 24, 2009 at 4:39 PM, James Bennett wrote: > Except this is what it turns into. So suppose a patch is added which > does nothing except keep the database connection open; well, that's > problematic because it means a server process/thread that's not > handling a

Re: Database connection closed after each request?

On Fri, Jul 24, 2009 at 1:31 AM, Glenn Maynard wrote: > I see no need for a complex connection pooling service.  You're making > this sound much more complicated than it is, resulting in people > needing to use configurations much more complicated than necessary. Except this is

Re: Database connection closed after each request?

On Thu, Jul 23, 2009 at 9:50 PM, Glenn Maynard wrote: > In this case, that's a terrible-performance-by-default approach. > (It's also not a default, but the only behavior, but I'll probably > submit a patch to add a setting for this if I don't hit any major > problems.) Please do

Re: Database connection closed after each request?

On Thu, Jul 23, 2009 at 10:02 PM, Carlos A. Carnero Delgado<carloscarn...@gmail.com> wrote: > On Thu, Jul 23, 2009 at 5:24 PM, Glenn Maynard<gl...@zewt.org> wrote: >> Why is each thread's database connection closed after each request? > > I believe that this is related

Re: Database connection closed after each request?

Hi, On Thu, Jul 23, 2009 at 5:24 PM, Glenn Maynard<gl...@zewt.org> wrote: > Why is each thread's database connection closed after each request? I believe that this is related to Django's shared-nothing-by-default approach. HTH, Carlos. --~--~-~--~~~---~--~

Database connection closed after each request?

Why is each thread's database connection closed after each request? Opening a database connection is expensive; it's taking 150ms. Even 10ms would be far too much, for a request that otherwise takes only 30ms. Django threads are reused in FastCGI, and database connections are reusable; why do