Re: Postgresql settings help for 8.0.1

Only thing I heard was turn off hyper threading.

Joel Fradkin

Wazagua, Inc.
2520 Trailmate Dr
Sarasota, Florida 34243
Tel.  941-753-7111 ext 305

jfradkin@wazagua.com
www.wazagua.com
Powered by Wazagua
Providing you with the latest Web-based technology & advanced tools.
C 2004. WAZAGUA, Inc. All rights reserved. WAZAGUA, Inc
 This email message is for the use of the intended recipient(s) and may
contain confidential and privileged information.  Any unauthorized review,
use, disclosure or distribution is prohibited.  If you are not the intended
recipient, please contact the sender by reply email and delete and destroy
all copies of the original message, including attachments.




-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Pallav Kalva
Sent: Wednesday, April 06, 2005 8:54 AM
To: pgsql-admin@postgresql.org
Subject: [ADMIN] Postgresql settings help for 8.0.1

Hi,

   I posted this message earlier but i didnt get any responses, i am
posting here again. We are migrating to a new server with more memory
and also from postgres 7.4 to postgres 8.0.1 version.

Here are my settings on the current 7.4 version:
OS : RedHat 9
CPUS: 2 hyperthreaded
Memory: 4gig
shared_buffers: 65536
sort_mem: 16384
vacuum_mem: 32768
wal_buffers: 64
effective_cache_size: 393216
checkpoint_segments: 3
checkpoint_timeout: 300
checkpoint_warning: 30

These are settings which I am planning on the new machine with 8.0.1
version:
OS: Fedora Core 2
CPUs: 2 hyperthreaded
Memory: 8 gig
shared_buffers: 131072
work_mem: 32768
maintanence_work_mem: 65536
wal_buffers: 64
effective_cache_size: 786432
checkpoint_segments: 8
checkpoint_timeout: 600
checkpoint_warning: 30

   The current settings on my 7.4 version gives me very good
performance, so I basically doubled the settings since i will be having
the double the memory in the new machine. What my concern is about the
effective_cache_settings , according the docs its recommends me to set
max to about 2/3 of the total memory and I went little over on top of
it, is that ok ? I went little over on my current 7.4 system too, and
its giving me very good performance so I used the same calculation for
my new system too.
  Also, can anyone guide me with the ideal settings for
vacuum_cost_delay, vacuum_cost_page_hit, vacuum_cost_page_miss,
vacuum_cost_page_dirty, vacuum_cost_limit,  background_delay,
bgwriter_percent, bgwriter_maxpages settings. I am not sure what
settings should I make to these parameters , are there any ideal
settings for these parameters in a OLTP environment ?

Thanks!
Pallav


---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match