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

Re: postgres on Windows

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Mark Steben <msteben(at)autorevenue(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: postgres on Windows
Date: 2009-12-28 20:56:05
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
2009/12/28 Mark Steben <msteben(at)autorevenue(dot)com>:
> Our 8.3.7 production environment is run on Linux operating systems.  We do,
> however
> Have our developers who keep a local copy of the database on their windows
> XP machines.
> One such developer has asked my help in configuring postgresql.conf to
> optimize his performance.
> The 8.3 documentation is very informative about setting Linux SYS 5
> parameters and
> giving insight to postgres memory consumption parms.  I can’t seem to find a
> lot of guidelines
> for Windows performance.
> The developer has 3 GB of ram and 130 GB hard drive.  Any insight,
> guidelines,
> Or any reference I can be pointed to would be most appreciated.

Tuning on windows is similar to running on linux, except that
increasing shared_buffer memory in windows shows fewer returns, and
only a few hundred meg is usually plenty.  Unless you're actively
working on sets larger than shared_buffers, don't crank it way up.

Look at turning up work_mem and maintenance_work_mem.
Lower random_page_cost and raise effective_cache_size, especially if
the dataset on the dev database will fit easily into memory.

If the data on the workstation isn't important, you can try turning
off fsync (warning, your data WILL get corrupted and lost if / when
windows crashes someday)  Or get most of the gain by turning off
synchronous_commit which makes it faster but keeps your data from
getting corrupted should the machine shut down unexpectedly.

In response to

pgsql-admin by date

Next:From: Tom LaneDate: 2009-12-30 20:36:17
Subject: Re: Getting::message type 0x43 arrived from server while idle
Previous:From: Scott MarloweDate: 2009-12-28 20:50:39
Subject: Re: Database performance problems

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