| From: | John Melesky <john(dot)melesky(at)rentrakmail(dot)com> |
|---|---|
| To: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: NFS, file system cache and shared_buffers |
| Date: | 2014-05-27 18:20:32 |
| Message-ID: | CAJ1GNCrqPY+mkfxAemPW+vx-hiC2pQNFJTTyfsx0bNZaid1EBg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, May 27, 2014 at 4:06 AM, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>wrote:
> I just learned that NFS does not use a file system cache on the client
> side.
>
That's ... incorrect. NFS is cache-capable. NFSv3 (I think? It may have
been v2) started sending metadata on file operations that was intended to
allow for client-side caches. NFSv4 added all sorts of stateful behavior
which allows for much more aggressive caching.
Where did you read that you could not use caching with NFS?
--
John Melesky | Sr Database Administrator
503.284.7581 x204 | john(dot)melesky(at)rentrak(dot)com <john(dot)melesky(at)rentrakmail(dot)com>
RENTRAK | www.rentrak.com | NASDAQ: RENT
Notice: This message is confidential and is intended only for the
recipient(s) named above. If you have received this message in error,
or are not the named recipient(s), please immediately notify the
sender and delete this message.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Grzegorz Olszewski | 2014-05-27 21:09:45 | Planner doesn't take indexes into account |
| Previous Message | Jeff Janes | 2014-05-27 16:54:23 | Re: NFS, file system cache and shared_buffers |