From: | Vick Khera <vivek(at)khera(dot)org> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | postgres cache vs ZFS cache |
Date: | 2014-01-31 15:04:49 |
Message-ID: | CALd+dcd07Q7ZBER+_BXo1RZnme0M3F7JhbhA_VdUQG868w2bPg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I'm looking at some performance tuning for a server running FreeBSD and the
DB on top of ZFS.
I keep reading the recommendation to turn off the primary data cache in ZFS
since postgres does its own caching. The recommendations also say to set
effective_cache_size to a significant amount of the RAM. The claim is that
this avoids double caching of the data.
My understanding from my past research is that effective_cache_size only
tells postgres how big the OS cache of the data on disk is, so there really
is no double cache. It is just a hint so it knows roughly how much to
expect the OS to hold on to.
Based on this understanding, I believe this recommendation to turn off the
ZFS primary cache for postgres data to be wrong. Or is there some other
place postgres is caching the data beyond the shared memory pool?
I find it mentioned here:
http://open-zfs.org/wiki/Performance_tuning#PostgreSQL among other places.
Thanks for any clarifications and advice here.
From | Date | Subject | |
---|---|---|---|
Next Message | Albe Laurenz | 2014-01-31 15:05:00 | Re: Temporary table already exists |
Previous Message | Adrian Klaver | 2014-01-31 15:04:48 | Re: Temporary table already exists |