From: Mark Nelson <mark.nelson@inktank.com>
To: "Shu, Xinxin" <xinxin.shu@intel.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: [RFC] add rocksdb support
Date: Mon, 03 Mar 2014 07:37:43 -0600 [thread overview]
Message-ID: <531485A7.4040408@inktank.com> (raw)
In-Reply-To: <75674D092A819E4189E91166C74CB90D0131CB27@SHSMSX104.ccr.corp.intel.com>
On 03/02/2014 08:07 PM, Shu, Xinxin wrote:
> Hi all,
>
> This patch added rocksdb support for ceph, enabled rocksdb for omap directory. Rocksdb source code can be get from link. To use use rocksdb, C++11 standard should be enabled, gcc version >= 4.7 is required to get C++11 support. Rocksdb can be installed with instructions described in the INSTALL.md file, and rocksdb header files (include/rocksdb/*) and library (librocksdb.so*) need to be copied to corresponding directories.
> To enable rocksdb, add "--with-librocksdb" option to configure. The rocksdb branch is here(https://github.com/xinxinsh/ceph/tree/rocksdb).
>
>
> Performance Test
> Attached file is the performance comparison of rocksdb and leveldb on four nodes with 40 osds, using 'rados bench' as the test tool. The performance results is quite promising.
>
> Any comments or suggestions are greatly appreciated.
Awesome job! Excited to look at this!
>
> Rados bench BandWidth(MB/s) Average latency
> Leveldb rocksdb Leveldb rocksdb
> write 4 threads 263.762 272.549 0.061 0.059
> write 8 threads 449.834 457.811 0.071 0.070
> write 16 threads 642.100 638.972 0.100 0.100
> write 32 threads 705.897 717.598 0.181 0.178
> write 64 threads 705.011 717.204 0.370 0.362
> read 4 threads 873.588 841.704 0.073 0.076
> read 8 threads 816.699 818.451 0.078 0.078
> read 16 threads 808.810 798.053 0.079 0.080
> read 32 threads 798.394 802.796 0.080 0.080
> read 64 threads 792.848 790.593 0.081 0.081
> --
> 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:[~2014-03-03 13:37 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 2:07 [RFC] add rocksdb support Shu, Xinxin
2014-03-03 13:37 ` Mark Nelson [this message]
2014-03-04 4:48 ` Alexandre DERUMIER
2014-03-04 8:41 ` Shu, Xinxin
2014-03-05 8:23 ` Alexandre DERUMIER
2014-03-05 8:30 ` Shu, Xinxin
2014-03-05 8:31 ` Haomai Wang
2014-03-05 9:19 ` Andreas Joachim Peters
2014-03-06 9:18 ` Shu, Xinxin
2014-05-21 1:19 ` Sage Weil
2014-05-21 12:54 ` Shu, Xinxin
2014-05-21 13:06 ` Mark Nelson
2014-05-28 10:05 ` Shu, Xinxin
2014-06-03 20:01 ` Sage Weil
2014-06-09 17:11 ` Mark Nelson
2014-06-10 4:59 ` Shu, Xinxin
2014-06-13 18:51 ` Sushma Gurram
2014-06-14 0:49 ` David Zafman
2014-06-14 3:49 ` Shu, Xinxin
2014-06-23 1:18 ` Shu, Xinxin
2014-06-23 7:32 ` Dan van der Ster
2014-06-27 0:44 ` Sushma Gurram
2014-06-27 3:33 ` Alexandre DERUMIER
2014-06-27 17:36 ` Sushma Gurram
2014-06-27 8:08 ` Haomai Wang
2014-07-01 0:39 ` Sushma Gurram
2014-07-01 6:10 ` Haomai Wang
2014-07-01 7:13 ` Somnath Roy
2014-07-01 8:05 ` Haomai Wang
2014-07-01 15:15 ` Sushma Gurram
2014-07-01 17:02 ` Haomai Wang
2014-07-01 23:49 ` Sushma Gurram
2014-07-02 12:56 ` Haomai Wang
2014-07-02 19:01 ` Sushma Gurram
2014-07-01 15:11 ` Sage Weil
2014-07-02 7:23 ` Shu, Xinxin
2014-07-02 13:07 ` Haomai Wang
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=531485A7.4040408@inktank.com \
--to=mark.nelson@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=xinxin.shu@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.