Hardware Tuning

From: Chris Gamache <cgg007(at)yahoo(dot)com>
To: pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Hardware Tuning
Date: 2002-08-13 18:37:15
Message-ID: 20020813183715.5406.qmail@web13805.mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-jdbc


I've read Bruce's white paper on Hardware Tuning. I'd like advise on squeezing
the most performance out of our database...

It is performing nicely with the settings below. There is no swapping to disk
going on, which makes me think I might be able to push the envelope even
further... Perhaps y'all could make some suggestions. :)

Dual P4 2.0GHz
1GB RDRAM
Linux Kernel 2.4.18
2 seperate 10000 RPM SCSI Filesystems
data files and WAL on seperate filesystems

---[postgresql.conf]-----------

max_connections = 32
shared_buffers = 256
sort_mem = 2048
fsync=false
effective_cache_size = 3000
wal_buffers = 8
wal_files = 32
wal_sync_method = fsync
wal_debug = 0
commit_delay = 0
commit_siblings = 5
checkpoint_segments = 3
checkpoint_timeout = 300

---[/postgresql.conf]-----------

I could post some system stats... Its biggest performance hit is when I do a
SELECT on non-indexed columns, which is not very often. I doubt there is much
that can be done about that (except for creating an index...)

CG

__________________________________________________
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Thomas O'Connell 2002-08-13 18:51:41 Re: performance tuning: shared_buffers, sort_mem; swap
Previous Message Thomas O'Connell 2002-08-13 18:20:16 Re: performance tuning: shared_buffers, sort_mem; swap

Browse pgsql-jdbc by date

  From Date Subject
Next Message Barry Lind 2002-08-13 19:06:48 Re: NAMEDATALEN going to 64
Previous Message Bruce Momjian 2002-08-13 18:26:12 NAMEDATALEN going to 64