On Mon, 2006-10-16 at 13:45 -0500, James Bennett wrote:
> On 10/16/06, Mike <[EMAIL PROTECTED]> wrote:
> > The server is rather new. 2GB of memory with a top grade Opteron (not
> > sure which). Once again, the server is running with low load for most
> > of the day, and as much as I want to, I hav
On 10/16/06, Mike <[EMAIL PROTECTED]> wrote:
> The server is rather new. 2GB of memory with a top grade Opteron (not
> sure which). Once again, the server is running with low load for most
> of the day, and as much as I want to, I have hard time believing its
> the server that is to blame.
FWIW,
On 10/16/06, Mike <[EMAIL PROTECTED]> wrote:
> I just svn update my django directory. Doesn't the latest django
> version reflect all the bug fixes? Do I have to check out
> 0.91-bugfixes?
The "bugfixes" branches are only for the older (0.90 and 0.91)
versions of Django, and I only mentioned them
On Monday 16 October 2006 18:01, Mike wrote:
> The server is rather new. 2GB of memory with a top grade Opteron (not
> sure which). Once again, the server is running with low load for most
> of the day, and as much as I want to, I have hard time believing its
> the server that is to blame.
But it
> Pressing 'c' on top clears everything a little bit. One thing
> I think I forgot to mention is 90% of the time the server load
> is moderate. It is 3 times a week around early in the morning
> that my django and postgres start dancing to death for me.
> Given that my server hardware handles the
> What are the specs of the server? Specifically, how much RAM does it
> have and how fast are its disks? What processors are in the machine
> (for postgres, Xeons are bad, Opterons are very, very good)?
The server is rather new. 2GB of memory with a top grade Opteron (not
sure which). Once agai
James,
Thanks for your response.
I just svn update my django directory. Doesn't the latest django
version reflect all the bug fixes? Do I have to check out
0.91-bugfixes?
Pressing 'c' on top clears everything a little bit. One thing I think I
forgot to mention is 90% of the time the server load
On 10/16/06, Siah <[EMAIL PROTECTED]> wrote:
> I tried increasing the number of postgres connections, and it ended up
> completely killing the server. The server I'm working with has 2 django
> sites running, one of which receives around 3M hits a month. The other
> one somewhere around 200K hits,
Per connection? Does it mean per request, or page view?
I tried increasing the number of postgres connections, and it ended up
completely killing the server. The server I'm working with has 2 django
sites running, one of which receives around 3M hits a month. The other
one somewhere around 200K h
On 10/16/06, Siah <[EMAIL PROTECTED]> wrote:
> How many postmaster instances should be running at once?
Also, if you're running an older version of Django, be sure to update
to the "bugfixes" branch for it; the mod_python handler had a bug in
it which could leak DB connections, and which has sinc
On 10/16/06, Siah <[EMAIL PROTECTED]> wrote:
> How many postmaster instances should be running at once?
Are you talking about 'postmaster', or 'postgres'? The default
behavior of top has a nasty habit of confusing the two; press 'c' to
have it show the full info.
That said, we have a bunch of po
Postgres uses one process per connection. How many simultaneous
connections have you got in total? If you don't have that many
simultaneous users then you may not be closing database connections
somewhere.
You can increase the number of connections that Postgres can handle,
but it looks like you
12 matches
Mail list logo
