0= Optimize your schema to be a tight as possible.  Your goal is to give 
yourself the maximum chance that everything you want to work on is in RAM when 
you need it.
1= Upgrade your RAM to as much as you can possibly strain to afford.  4GB at 
least.  It's that important.
2= If the _entire_ DB does not fit in RAM after upgrading your RAM, the next 
step is making sure your HD IO subsystem is adequate to your needs.
3= Read the various pg tuning docs that are available and Do The Right Thing.
4= If performance is still not acceptable, then it's time to drill down into 
what specific actions/queries are problems.
If you get to here and the entire DBMS is still not close to acceptable, your 
fundamental assumptions have to be re-examined.


-----Original Message-----
From: Yves Vindevogel <[EMAIL PROTECTED]>
Sent: Nov 9, 2005 3:11 PM
To: pgsql-performance@postgresql.org
Subject: [PERFORM] Some help on buffers and other performance tricks

Hi all,

I've got PG 8.0 on Debian sarge set up ...
I want to speed up performance on the system.

The system will run PG, Apache front-end on port 80 and Tomcat / Cocoon 
for the webapp.
The webapp is not so heavily used, so we can give the max performance 
to the database.
The database has a lot of work to do, we upload files every day.
The current server has 8 databases of around 1 million records.  This 
will be more in the future.
There's only one main table, with some smaller tables.  95% of the 
records are in that one table.
A lot of updates are done on that table, affecting 10-20% of the 

The system has 1 gig of ram.  I could give 512Mb to PG.
Filesystem is ext2, with the -noatime parameter in fstab

Could I get some suggestions in how to configure my buffers, wals, .... 

Met vriendelijke groeten,
Bien � vous,
Kind regards,

Yves Vindevogel

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Reply via email to