From: Skottie Miller <skottie@anim.dreamworks.com>
To: Bogdan Costescu <bogdan.costescu@iwr.uni-heidelberg.de>
Cc: Jake Gold <jake@dtiserv2.com>,
James Pearson <james-p@moving-picture.com>,
Charles.Lever@netapp.com, nfs@lists.sourceforge.net
Subject: Re: NFSv4 and client caching to local disk?
Date: Tue, 01 Apr 2003 11:56:56 -0800 [thread overview]
Message-ID: <3E89EF08.2050401@anim.dreamworks.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0304012046510.5929-100000@kenzo.iwr.uni-heidelberg.de>
Bogdan Costescu wrote:
> On Mon, 31 Mar 2003, Jake Gold wrote:
>
>>I have a FAS940 with a cluster of Linux machines mounting _read-only_
>>volumes over NFSv3. My situation is the same as James Pearson's....those
>>machines read large, rarely modified files, where memory caching doesn't
>>help a whole lot. It would be very nice to be able to have my
>>under-worked local disks take some of the load off the filer.
>
> How about doing it in the application itself ? Often application has more
> knowledge about what it needs than the OS. So in a case like the one that
> you described I would copy the rarely modified file(s) to the local disk
> and just before accessing them in any way check to see if they were
> modified. If this is true read-only you don't even need to check this, but
> otherwise you could use some rsync-style transfer to get only the parts
> that were modified (assuming that new data is not completely different)...
> Modification can be detected from the file attributes, md5sum or something
> else.
We do the caching to compute-node local disk, via the applications when we can.
But two things often make that difficult: (1) the working set of the cached data
is larger than the compute-note local disk, and (2) we don't own all the applications.
So, I complement the compute-node local disk caches (and sometimes replace them)
with a series of NetCache c2100 dNFS boxes. The origin data is on 960's,
which serve up their data to the user workstations, and to the caches.
The renderfarm compute nodes get almost all their high-traffic read-only
data off the caches. This maintains good interactive performance for the
user workstations and keeps the renderfarm fed.
-skottie
--
Scott Miller | Animation Technology
work: skottie@dreamworks.com | Dreamworks Feature Animation
life: skottie@pobox.com
-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb:
Dedicated Hosting for just $79/mo with 500 GB of bandwidth!
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-04-01 19:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 15:16 NFSv4 and client caching to local disk? Lever, Charles
2003-03-31 12:33 ` James Pearson
2003-03-31 18:38 ` Jake Gold
2003-04-01 19:05 ` Bogdan Costescu
2003-04-01 19:56 ` Skottie Miller [this message]
2003-04-02 11:27 ` Bogdan Costescu
2003-04-02 11:56 ` James Pearson
2003-04-01 20:56 ` James Pearson
2003-04-01 20:59 ` Jake Gold
-- strict thread matches above, loose matches on Subject: below --
2003-04-03 16:31 Brashers_Per
2003-03-31 21:50 Lever, Charles
2003-04-01 0:03 ` Jake Gold
2003-03-31 19:44 Peter Åstrand
2003-03-28 12:22 James Pearson
2003-03-28 15:01 ` J. Bruce Fields
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E89EF08.2050401@anim.dreamworks.com \
--to=skottie@anim.dreamworks.com \
--cc=Charles.Lever@netapp.com \
--cc=bogdan.costescu@iwr.uni-heidelberg.de \
--cc=jake@dtiserv2.com \
--cc=james-p@moving-picture.com \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.