All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ric Wheeler <rwheeler@redhat.com>
To: Miguel Sousa Filipe <miguel.filipe@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: FileSystem level compression support.
Date: Wed, 11 Jun 2008 09:42:34 -0400	[thread overview]
Message-ID: <484FD64A.8000106@redhat.com> (raw)
In-Reply-To: <f058a9c30806110413y39102d33t98cd685f289beb2d@mail.gmail.com>

Miguel Sousa Filipe wrote:
> Hi there,
>
> Providing compression and/or encryption at the file system layer has
> proven to be contentious and polemic, at least in the linux kernel
> world.
>
> However, I would like to probe you guys (specially Chis Mason) about
> your thoughts on the issue.
> I have seen quite a few benchs were compression provides better
> performance, since it reduces the amount of IO.
> It seems to be a cpu/io trade-off. And given that cpu power is more
> easily accessible than fast IO.. it is starting to look a good idea
> that should be more deeply explored.
>
> Is compression for data on BTRFS a feature that is:
> - completely out of the table - it will not happen at the BTRFS layer
> - considered, but no efforts on developing this feature are planed.
> - considered, and design decisions are contemplating it.. but no code
> yet.. not this soon. (not for 1.0)
>
>
> Kind regards!
>
>   
One big issue with compression is that it is very workload dependent. 
For example, if you are storing lots of video, sound or image files, the 
format itself it normally already compressed so you end up doing nothing 
but burning CPU cycles ;-) Also, for very small files, compression works 
best when you bunch them up (say compress the contents of a subdirectory).

Also note that some storage devices can do compression for you beneath 
the file system or do other fancy features like block level data 
de-duplication.

ric


  reply	other threads:[~2008-06-11 13:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-11 11:13 FileSystem level compression support Miguel Sousa Filipe
2008-06-11 13:42 ` Ric Wheeler [this message]
2008-06-11 14:20 ` Chris Mason

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=484FD64A.8000106@redhat.com \
    --to=rwheeler@redhat.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=miguel.filipe@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 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.