On Jan 30, 2008 8:55 PM, Mark Green <[EMAIL PROTECTED]> wrote:
> What ressources are held and wasted exactly?
> Maintaining a number of open TCP connection is much cheaper
> than creating/discarding them at a high rate.
Every connection that one Django application holds on to is a
connection that
On Wed, 2008-01-30 at 19:34 -0600, James Bennett wrote:
> On Jan 30, 2008 6:01 PM, Mark Green <[EMAIL PROTECTED]> wrote:
> > Ahem, there's a huge difference between being confronted with
> > a spinner/progress bar or an error page. The former speaks
> > "Please wait", the latter speaks "Try again"
On Jan 30, 2008 6:01 PM, Mark Green <[EMAIL PROTECTED]> wrote:
> Ahem, there's a huge difference between being confronted with
> a spinner/progress bar or an error page. The former speaks
> "Please wait", the latter speaks "Try again".
OK, so let's break this down.
There are two potential cases
On Wed, 2008-01-30 at 11:03 -0600, James Bennett wrote:
> On Jan 30, 2008 8:57 AM, Mark Green <[EMAIL PROTECTED]> wrote:
> > Well, "Build for failure". Temporary overload can happen at any
> > time and I'd expect django to behave exceptionally bad in that
> > case as it is.
>
> Running out of res
On Jan 30, 2008 8:57 AM, Mark Green <[EMAIL PROTECTED]> wrote:
> Well, "Build for failure". Temporary overload can happen at any
> time and I'd expect django to behave exceptionally bad in that
> case as it is.
Running out of resources is never a good thing for any system.
> Disclaimer: I haven'
On Tue, 2008-01-29 at 23:33 -0600, James Bennett wrote:
> On Jan 29, 2008 11:18 PM, Mark Green <[EMAIL PROTECTED]> wrote:
> > I agree on the loadbalancer front but the overhead for all
> > those TCP connections (and pgpool managing them) worries me a bit.
>
> I've used pgpool in production with g
On Jan 29, 2008 11:18 PM, Mark Green <[EMAIL PROTECTED]> wrote:
> I agree on the loadbalancer front but the overhead for all
> those TCP connections (and pgpool managing them) worries me a bit.
I've used pgpool in production with great success, so I'm not really
sure what overhead you're talking
On Tue, 2008-01-29 at 22:07 -0600, James Bennett wrote:
> On Jan 29, 2008 10:04 PM, Mark Green <[EMAIL PROTECTED]> wrote:
> > Just curious, what's the state of connection pooling in django?
>
> My personal opinion is that the application level (e.g., Django) is
> the wrong place for connection p
On Jan 29, 2008 10:04 PM, Mark Green <[EMAIL PROTECTED]> wrote:
> Just curious, what's the state of connection pooling in django?
My personal opinion is that the application level (e.g., Django) is
the wrong place for connection pooling and for the equivalent "front
end" solution of load balancin
On Fri, 2008-01-25 at 15:14 -0800, Jacob Kaplan-Moss wrote:
> Hi Doug --
>
> On 1/24/08, Doug Van Horn <[EMAIL PROTECTED]> wrote:
> > OperationalError: could not connect to server: No such file or
> > directory
> >Is the server running locally and accepting
> >connections on Unix
Hi Doug --
On 1/24/08, Doug Van Horn <[EMAIL PROTECTED]> wrote:
> OperationalError: could not connect to server: No such file or
> directory
>Is the server running locally and accepting
>connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.
> 5432"?
This means that, fo
I recieve the following error very *occasionally* from a couple of
different django apps running against Postgres (some backtrace
included for context):
File "/opt/django/trunk/django/db/models/query.py", line 188, in
iterator
cursor = connection.cursor()
File "/opt/django/trunk/django/db/b
12 matches
Mail list logo
