| From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "John Melesky *EXTERN*" <john(dot)melesky(at)rentrakmail(dot)com> |
| 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-28 07:50:40 |
| Message-ID: | A737B7A37273E048B164557ADEF4A58B17CFE9E2@ntex2010i.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
John Melesky 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.
What do you mean by "allows"? Does it cache files in memory or not?
Do you need additional software? Special configuration?
> Where did you read that you could not use caching with NFS?
I have it by hearsay from somebody who seemed knowledgable, and the
existence of CacheFS seemed to indicate it was true.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Albe Laurenz | 2014-05-28 08:41:18 | Re: NFS, file system cache and shared_buffers |
| Previous Message | AI Rumman | 2014-05-27 21:14:21 | Re: Planner doesn't take indexes into account |