All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Pearson <james-p@moving-picture.com>
To: Bogdan Costescu <bogdan.costescu@iwr.uni-heidelberg.de>
Cc: nfs@lists.sourceforge.net
Subject: Re: NFSv4 and client caching to local disk?
Date: Wed, 02 Apr 2003 12:56:28 +0100	[thread overview]
Message-ID: <3E8ACFEC.360E46FB@moving-picture.com> (raw)
In-Reply-To: Pine.LNX.4.44.0304021313460.13935-100000@kenzo.iwr.uni-heidelberg.de

Bogdan Costescu wrote:
> 
> On Tue, 1 Apr 2003, Skottie Miller wrote:
> 
> > 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,
> 
> Ah, so you define now a working set which is a subset of the whole data
> set. In this case I would say that you can't win in any situation; it's
> similar to a process that needs memory larger than RAM and has to use the
> disk - either the OS does swapping or the process itself writes parts of
> its memory to the disk, but it has to be done continuously as the process
> jumps through memory - the disk is used in any case and the performance
> is lowered... Buy larger disks :-)
> 
> > (2) we don't own all the applications.
> 
> Yes, obviously this is a problem and can only be solved if you are a big
> enough customer for the software company :-)
> 
> But there might be some other problem: if the data set that is mostly read
> only is needed on most or all clients, updating it on the server will
> generate in a very short time a storm of requests for transfers of the new
> content. If you are using some blind OS level caching, this will create a
> big load on the server or network congestion because most or all clients
> will try to get the new data. With application level caching you might do
> nice stuff like using some priority lists, using one client that already
> got the data to send it to another client, etc.
> 

I would like to have some blind OS level caching as a starting point ...
then use some higher level application to seed the cache. In this way,
the 3rd party application doesn't need to be altered and can just get
its data from the OS's cached copy ...

James Pearson


-------------------------------------------------------
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

  reply	other threads:[~2003-04-02 11: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
2003-04-02 11:27         ` Bogdan Costescu
2003-04-02 11:56           ` James Pearson [this message]
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=3E8ACFEC.360E46FB@moving-picture.com \
    --to=james-p@moving-picture.com \
    --cc=bogdan.costescu@iwr.uni-heidelberg.de \
    --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.