From: Mark Nelson <mark.nelson@inktank.com>
To: Chris Pacejo <cpacejo@clearskydata.com>,
"Chen, Xiaoxi" <xiaoxi.chen@intel.com>
Cc: Haomai Wang <haomaiwang@gmail.com>, Sage Weil <sage@newdream.net>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: [ceph-users] keyvaluestore backend metadata overhead
Date: Tue, 03 Feb 2015 21:15:38 -0600 [thread overview]
Message-ID: <54D18EDA.6020901@redhat.com> (raw)
In-Reply-To: <CAC8iE5iLJ53AS4+AH-2F+NCVwf5h7oVcb79bTPMZQQY3VAu0fA@mail.gmail.com>
On 02/03/2015 09:03 AM, Chris Pacejo wrote:
> Hi Xiaoxi,
>
> On Sun, Feb 1, 2015 at 9:50 AM, Chen, Xiaoxi <xiaoxi.chen@intel.com> wrote:
>> We can always use a structure database in an unstructured way, I think it's workable in theory, but why choose MySQL?
>
> In our internal performance tests, it performed better than LevelDB
> and some others, and it's well-proven. It's not our first choice, nor
> are we done investigating other options. But we'll check out LMDB,
> thanks for the pointer.
>
> Regardless, the issues we're seeing are equally applicable to any
> key-value backend.
You may also wish to try the rocksdb backend with universal compaction
rather than leveled compaction.
> --
> 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:[~2015-02-04 3:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAC8iE5iHTEfSQL978paWpu9hSfUbE65OVT_dKi2P=yvWSQ5JhA@mail.gmail.com>
2015-01-29 22:51 ` [ceph-users] keyvaluestore backend metadata overhead Sage Weil
2015-01-30 2:46 ` Haomai Wang
2015-01-30 15:41 ` Chris Pacejo
2015-01-30 15:52 ` Haomai Wang
2015-01-30 16:08 ` Chris Pacejo
2015-01-30 16:18 ` Haomai Wang
2015-02-01 14:50 ` Chen, Xiaoxi
2015-02-03 15:03 ` Chris Pacejo
2015-02-04 3:15 ` Mark Nelson [this message]
2015-02-03 15:13 ` Chris Pacejo
2015-02-03 20:25 ` Chris Pacejo
2015-02-04 2:31 ` Haomai Wang
2015-02-09 18:29 ` Chris Pacejo
2015-02-10 6:33 ` Haomai Wang
2015-01-30 14:46 ` Chris Pacejo
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=54D18EDA.6020901@redhat.com \
--to=mark.nelson@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=cpacejo@clearskydata.com \
--cc=haomaiwang@gmail.com \
--cc=mnelson@redhat.com \
--cc=sage@newdream.net \
--cc=xiaoxi.chen@intel.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.