linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bfields@fieldses.org (J. Bruce Fields)
To: Cedric Blancher <cedric.blancher@gmail.com>
Cc: Martin Houry <martinhoury@gmail.com>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: Question : Compress files to send with NFS4.1
Date: Thu, 7 Apr 2016 14:16:44 -0400	[thread overview]
Message-ID: <20160407181644.GC30676@fieldses.org> (raw)
In-Reply-To: <CALXu0UfC3h2Rv4oQ9pSZLeMQJMqQu4zt2ywTBTMiWhmD9S6sfg@mail.gmail.com>

On Thu, Apr 07, 2016 at 04:06:11PM +0200, Cedric Blancher wrote:
> On 7 April 2016 at 15:27, Martin Houry <martinhoury@gmail.com> wrote:
> > Is NFS4.1 capable to compress files before sending them on the network
> > and decompress them on the destination to speed up the file transfert?
> 
> You can get that with IP tunnel compression. Trouble is, NFS
> (v2/v3/v4; and younger protocol designers are even worse by telling
> you 'dunno care about high latency [ > 4 sec roundtrip ] any more'
> [yeah? wanna pester? old RFS and AFS did a better job...]) are highly
> sensitive to latency, and like ssh the high latency causes more
> trouble than its worth.

The only feature the protocol has that's a little bit like compression
is READ_PLUS (in 4.2), which can tell the client that a range of the
file is a hole instead of returning all the zeroes.  You could think of
that as a specialized kind of compression for sparse files.  Even there
we've been having some trouble ensuring there aren't performance
regressions.

--b.

      reply	other threads:[~2016-04-07 18:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-07 13:27 Question : Compress files to send with NFS4.1 Martin Houry
2016-04-07 14:06 ` Cedric Blancher
2016-04-07 18:16   ` J. Bruce Fields [this message]

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=20160407181644.GC30676@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=cedric.blancher@gmail.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=martinhoury@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).