From: "Piotr Dałek" <branch@predictor.org.pl>
To: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Initial proposal for bluestore compression control and statistics
Date: Fri, 20 May 2016 16:14:00 +0200 [thread overview]
Message-ID: <20160520141400.GA5041@predictor> (raw)
In-Reply-To: <4c89f7ee-bff1-8a9a-096a-c9459aba992b@mirantis.com>
On Fri, May 20, 2016 at 04:52:18PM +0300, Igor Fedotov wrote:
>
> On 19.05.2016 20:57, Piotr Dałek wrote:
> >I would also add ability to set minimum acceptable compression ratio,
> >with at least two options (any and no-expand). "Any" would store compressed
> >objects regardless how well they've compressed and "No-expand" would store
> >object in compressed format only if compressed size is smaller than
> >uncompressed size.
>
> Why do we need "Any" option? Isn't "No-expand" enough?
For example, when someone wants to benchmark Bluestore compression in worst case
scenario, or when someone wants to use compression as data-masking technique. And
finally, "no-expand" implies additional code in compressor/decompressor code
path and this option would go around it.
(Not particularly practical uses, but there might be someone who finds this
useful... and it's not difficult to do in code).
--
Piotr Dałek
branch@predictor.org.pl
http://blog.predictor.org.pl
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-05-20 14:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 17:27 Initial proposal for bluestore compression control and statistics Igor Fedotov
2016-05-19 17:57 ` Piotr Dałek
2016-05-20 13:52 ` Igor Fedotov
2016-05-20 14:14 ` Piotr Dałek [this message]
2016-05-19 19:40 ` Sage Weil
2016-05-19 20:52 ` Sage Weil
2016-05-20 14:36 ` Igor Fedotov
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=20160520141400.GA5041@predictor \
--to=branch@predictor.org.pl \
--cc=ceph-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.