Skip site navigation (1) Skip section navigation (2)

Re: postgreSQL performance 8.2.6 vs 8.3.3

From: David Rees <drees76(at)gmail(dot)com>
To: Battle Mage <battlemage(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: postgreSQL performance 8.2.6 vs 8.3.3
Date: 2009-02-20 21:46:00
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
On Fri, Feb 20, 2009 at 1:34 PM, Battle Mage <battlemage(at)gmail(dot)com> wrote:
> The amount of tps almost doubled, which is good, but i'm worried about the
> load.  For my application, a load increase is bad and I'd like to keep it
> just like in 8.2.6 (a load average between 3.4 and 4.3).  What parameters
> should I work with to decrease the resulting load average at the expense of
> tps?

Why is it bad?  High load can mean a number of things.

The only way to reduce the load is to get the client to submit
requests slower.  I don't think you'll be successful in tuning the
database to run slower.  I think you're headed in the wrong direction.


In response to


pgsql-performance by date

Next:From: Robert HaasDate: 2009-02-20 21:54:58
Subject: Re: Benchmark comparing PostgreSQL, MySQL and Oracle
Previous:From: Kenneth MarshallDate: 2009-02-20 21:45:50
Subject: Re: postgreSQL performance 8.2.6 vs 8.3.3

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group