From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | "kevin kempter" <kevin(at)kevinkempterllc(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Setting Effective Cache Size |
Date: | 2008-09-16 18:50:28 |
Message-ID: | dcc563d10809161150g76cb96eev6cd78d2618ca64d7@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Tue, Sep 16, 2008 at 9:30 AM, kevin kempter
<kevin(at)kevinkempterllc(dot)com> wrote:
> Hi All;
>
> Is there an easy way to determine the actual OS disk cache size or at least
> a set of guidelines based on the OS and disk subsystem type ?
On a DB only machine, you can expect the OS to use most of the spare
memory for disk cache eventually. So, if you've got a 16Gig machine
and pgsql and the OS are using ~ 2 Gigs or so, the effective cache
size will be what's left.
OTOH, if the machine does other things (file / print server, web
server, etc...) then you kinda have to fudge factor it. Generally
pgsql will still use more disk cache than those other things, due to
having more disk access going on all the time, but really it depends
on your usage patterns.
Luckily Effective cache size is a big course knob so being off by a
gig or three isn't a really big deal.
From | Date | Subject | |
---|---|---|---|
Next Message | Kenneth Marshall | 2008-09-16 18:58:00 | Re: Help request: how to tune performance? |
Previous Message | Scott Marlowe | 2008-09-16 17:30:19 | Re: Heavy postgres process |