Re: Postgres Performance Tuning

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Adarsh Sharma <adarsh(dot)sharma(at)orkash(dot)com>
Cc: Raghavendra <raghavendra(dot)rao(at)enterprisedb(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Postgres Performance Tuning
Date: 2011-04-05 13:08:07
Message-ID: BANLkTi=GhO3SaXgy7SweHHTO2zTGkLO23Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Tue, Apr 5, 2011 at 1:33 AM, Adarsh Sharma <adarsh(dot)sharma(at)orkash(dot)com> wrote:
>
> [root(at)s8-mysd-2 ~]# free -m
>            total       used       free     shared    buffers     cached
> Mem:         15917      15826         90          0        101      15013
> -/+ buffers/cache:        711      15205
> Swap:        16394        143      16250
>
> It means 15 GB memory is cached.

Note that the kernel takes all otherwise unused memory and uses it for
cache. If, at any time a process needs more memory, the kernel just
dumps some cached data and frees up the memory and hands it over, it's
all automatic. As long as cache is large, things are OK. You need to
be looking to see if you're IO bound or CPU bound first. so, vmstat
(install the sysstat package) is the first thing to use.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Adarsh Sharma 2011-04-05 13:20:05 Re: Postgres Performance Tuning
Previous Message Ákos Gábriel 2011-04-05 12:38:51 Re: Postgres Performance Tuning