On 7/9/07, Santhosh <[EMAIL PROTECTED]> wrote: > Im working on a small web-app using django. The problem is.. the > database operations are too slow. I think it may be because django > makes a new connection and authenticates etc.. to the db everytime it > wants something..Is there some way i can make django use a single > connection throughout and it shud terminate the connection only when i > want it to..
Django initiates a new connection on each incoming request, and closes it at the end of the request when it's sending out a response. There's really no way to alter that behavior in Django, though a pooling connection manager between Django and your database can be a great help if this is really where your overhead is coming from. I'd be curious, though, to know what led you to suspect this as the problem (since plenty of sites do just fine at a variety of levels of traffic without doing anything special for pooling connections): have you done any profiling to verify that this really is where the performance problems are? -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
