pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Tuning Postgresql on Windows XP Pro 32 bit [was on HACKERS list]
2+ messages / 2 participants
[nested] [flat]

* Tuning Postgresql on Windows XP Pro 32 bit [was on HACKERS list]
@ 2008-01-15 17:05  Doug Knight <dknight@wsi.com>
  0 siblings, 1 reply; 2+ messages in thread

From: Doug Knight @ 2008-01-15 17:05 UTC (permalink / raw)
  To: pgsql-performance

All,
I have been asked to move this thread to the performance list. Below is
the full discussion to this point.

Doug Knight
WSI Corp
Andover, MA

-------- Forwarded Message --------
From: Doug Knight <dknight@wsi.com>
To: munir.usama@gmail.com
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Tuning Postgresql on Windows XP Pro 32 bit
Date: Tue, 15 Jan 2008 09:09:16 -0500

We tried reducing the memory footprint of the postgres processes, via
shared_buffers (from 30000 on Linux to 3000 on Windows), max_fsm_pages
(from 2000250 on Linux to 100000 on Windows), max_fsm_relations (from
20000 on Linux to 5000 on Windows), and max_connections (from 222 on
Linux to 100 on Windows). Another variable we played with was
effective_cache_size  (174000 on Linux, 43700 on Windows). None of these
reduced memory usage, or improved performance,  significantly. We still
see the high page fault rate too. Other things we tried were reducing
the number of WAL buffers, and changing the wal_sync_method to
opendata_sync, all with minimal effect. I've attached the latest version
of our Windows postgresql.conf file.

Doug



On Mon, 2008-01-07 at 19:49 +0500, Usama Dar wrote: 

> Doug Knight wrote:
> > We are running the binary distribution, version 8.2.5-1, installed on 
> > Windows XP Pro 32 bit with SP2. We typically run postgres on linux, 
> > but have a need to run it under windows as well. Our typical admin 
> > tuning for postgresql.conf doesn't seem to be as applicable for windows.
> 
> 
> So what have you tuned so far? what are your current postgresql settings 
> that you have modified? What are your system specs for Hardware, RAM , 
> CPU etc?
> 
> 
> On Sun, 2008-01-06 at 18:23 +0500, Usama Dar wrote:
> 
> 
> 
> On Jan 3, 2008 8:57 PM, Doug Knight <dknight@wsi.com> wrote:
> 
>         All,
>         Is there a place where I can find information about tuning
>         postgresql running on a Windows XP Pro 32 bit system? I
>         installed using the binary installer. I am seeing a high page
>         fault delta and total page faults for one of the postgresql
>         processes. Any help would be great. 
>         
>         
> 
> 
> Which version of postgres? the process you are seeing this for is a
> user process? 
> 
> 
> 
> -- 
> Usama Munir Dar http://www.linkedin.com/in/usamadar
> Consultant Architect
> Cell:+92 321 5020666
> Skype: usamadar 

^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: Tuning Postgresql on Windows XP Pro 32 bit [was on HACKERS list]
@ 2008-01-18 22:50  Kevin Grittner <Kevin.Grittner@wicourts.gov>
  parent: Doug Knight <dknight@wsi.com>
  0 siblings, 0 replies; 2+ messages in thread

From: Kevin Grittner @ 2008-01-18 22:50 UTC (permalink / raw)
  To: pgsql-performance; Doug Knight <dknight@wsi.com>

>>> On Tue, Jan 15, 2008 at 11:05 AM, in message
<camel@arc-dknightlx.wsicorp.com/">1200416720.4742.6.camel@arc-dknightlx.wsicorp.com>, Doug Knight
<dknight@wsi.com> wrote: 
 
> We tried reducing the memory footprint of the postgres processes, via
> shared_buffers (from 30000 on Linux to 3000 on Windows),
 
I would never go below 10000.  20000 to 30000 is a good start.
 
> max_fsm_pages (from 2000250 on Linux to 100000 on Windows)
> max_fsm_relations (from 20000 on Linux to 5000 on Windows)
 
Figure out what you need and use that.  Low values can cause bloat.
Check the output of VACUUM ANALYZE VERBOSE (for the database)
for a line like this:
 
INFO:  free space map contains 717364 pages in 596 relations
 
> and max_connections (from 222 on Linux to 100 on Windows).
 
If you don't need more than 100, good.
 
> Another variable we played with was effective_cache_size
> (174000 on Linux, 43700 on Windows).
 
Figure out how much space is available to cache data,
counting both the shared buffers and the Windows cache.
This setting has no affect on memory usage, just the planner.
 
> On Mon, 2008-01-07 at 19:49 +0500, Usama Dar wrote: 
> 
>> Doug Knight wrote:
>> > We are running the binary distribution, version 8.2.5-1, installed on 
>> > Windows XP Pro 32 bit with SP2. We typically run postgres on linux, 
>> > but have a need to run it under windows as well. Our typical admin 
>> > tuning for postgresql.conf doesn't seem to be as applicable for windows.
>> 
>> So what have you tuned so far? what are your current postgresql settings 
>> that you have modified? What are your system specs for Hardware, RAM , 
>> CPU etc?
 
I would add that you should post what problems you're seeing.
 
>>         Is there a place where I can find information about tuning
>>         postgresql running on a Windows XP Pro 32 bit system? I
>>         installed using the binary installer. I am seeing a high page
>>         fault delta and total page faults for one of the postgresql
>>         processes.
 
Are those "hard" or "soft" page faults.  There's a big difference.
Review Windows docs for descriptions and how to check.
You may not be able to do much about soft page faults,
and they may not have much impact on your performance.
 
We abandoned Windows for database servers after testing
identical processing on identical hardware -- Linux was twice
as fast.  If you really need to run under Windows, you may need
to adjust your performance expectations.
 
-Kevin
 




^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2008-01-18 22:50 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2008-01-15 17:05 Tuning Postgresql on Windows XP Pro 32 bit [was on HACKERS list] Doug Knight <dknight@wsi.com>
2008-01-18 22:50 ` Kevin Grittner <Kevin.Grittner@wicourts.gov>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox