All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: Evgeniy <iron.udjin@gmail.com>
Cc: reiserfs-devel <reiserfs-devel@vger.kernel.org>
Subject: Re: Snappy compression algorithm for Reiser4.
Date: Sun, 22 Sep 2013 01:50:29 +0200	[thread overview]
Message-ID: <523E30C5.2090705@gmail.com> (raw)
In-Reply-To: <CAL2jS+=3q7Nvw89g=17Hj8uP-Cj_OtZ7R=QZRBDBz0Dknhhuug@mail.gmail.com>

21.09.2013 23:12, Evgeniy пишет:
> Hello all,
>
> Last few days I was playing a little bit around implementation Snappy
> algo in Reiser4. My code is dirty and should be optimized. But it's
> enough for testing.
> According to my tests Snappy shows near the same prefomance as LZO. In
> some kind of situations Snappy shows better compression with the less
> CPU usage.
> LZO has a few advantages over Snappy:
> 1) It's in kernel by default
> 2) It's optimized better then Snappy.
> Also a very significant fact is we're plaing with small blocks of
> data. In this case results of all algorithms looks near the same.
>
> Maybe in the future I'll reqrite a little bit BratSinot's LZ4 patch
> (http://sourceforge.net/p/reiser4/discussion/general/thread/780facb4/)
> to make it use LZ4 library which is build-in kernel. Friendly
> speaking, I'm not expect any big difference in comparison with LZO.
> But in any case, it funny :)


Support of a new compression algorithm means a format change.
So, people with roots on reiser4 will be forced to fsck their partitions.
So, not so funny.  A visible advantage in some benchmarks is highly
desirable..

Thanks,
Edward.


>
> If anybody want to test Snappy compression algo - let me know, I'll
> make patches to kernel and reiser4progs.
>
> Have a nice [the time of the day],
> Thanks
> --
> To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2013-09-21 23:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-21 21:12 Snappy compression algorithm for Reiser4 Evgeniy
2013-09-21 23:50 ` Edward Shishkin [this message]
2013-09-25 19:52   ` Edward Shishkin
2013-09-25 21:04     ` Evgeniy
2013-09-25 21:10     ` Chris Gentile
2013-09-25 21:12     ` Chris Gentile

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=523E30C5.2090705@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=iron.udjin@gmail.com \
    --cc=reiserfs-devel@vger.kernel.org \
    /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.