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

Re: Memory Allocation

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Ryan Hansen" <ryan(dot)hansen(at)brightbuilders(dot)com>,"pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>,"Scott Carey" <scott(at)richrelevance(dot)com>
Subject: Re: Memory Allocation
Date: 2008-11-26 23:09:15
Message-ID: 492D82BB.EE98.0025.0@wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-performance
>>> Scott Carey <scott(at)richrelevance(dot)com> wrote: 
> Set swappiness to 0 or 1.
 
We recently converted all 72 remote county databases from 8.2.5 to
8.3.4.  In preparation we ran a test conversion of a large county over
and over with different settings to see what got us the best
performance.  Setting swappiness below the default degraded
performance for us in those tests for identical data, same hardware,
no other changes.
 
Our best guess is that code which really wasn't getting called got
swapped out leaving more space in the OS cache, but that's just a
guess.  Of course, I'm sure people would not be recommending it if
they hadn't done their own benchmarks to confirm that this setting
actually improved things in their environments, so the lesson here is
to test for your environment when possible.
 
-Kevin

In response to

Responses

pgsql-performance by date

Next:From: Scott CareyDate: 2008-11-26 23:52:44
Subject: Re: Memory Allocation
Previous:From: Scott CareyDate: 2008-11-26 23:00:26
Subject: Re: Memory Allocation

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