All of lore.kernel.org
 help / color / mirror / Atom feed
From: Somnath Roy <Somnath.Roy@sandisk.com>
To: Mark Nelson <mnelson@redhat.com>,
	ceph-devel <ceph-devel@vger.kernel.org>
Subject: RE: Ceph Hackathon: More Memory Allocator Testing
Date: Wed, 19 Aug 2015 05:36:52 +0000	[thread overview]
Message-ID: <755F6B91B3BE364F9BCA11EA3F9E0C6F2CE1171B@SACMBXIP01.sdcorp.global.sandisk.com> (raw)
In-Reply-To: <55D409F0.3050802@redhat.com>

Mark,
Thanks for verifying this. Nice report !
Since there is a big difference in memory consumption with jemalloc, I would say a recovery performance data or client performance data during recovery would be helpful.

Thanks & Regards
Somnath

-----Original Message-----
From: ceph-devel-owner@vger.kernel.org [mailto:ceph-devel-owner@vger.kernel.org] On Behalf Of Mark Nelson
Sent: Tuesday, August 18, 2015 9:46 PM
To: ceph-devel
Subject: Ceph Hackathon: More Memory Allocator Testing

Hi Everyone,

One of the goals at the Ceph Hackathon last week was to examine how to improve Ceph Small IO performance.  Jian Zhang presented findings showing a dramatic improvement in small random IO performance when Ceph is used with jemalloc.  His results build upon Sandisk's original findings that the default thread cache values are a major bottleneck in TCMalloc 2.1.  To further verify these results, we sat down at the Hackathon and configured the new performance test cluster that Intel generously donated to the Ceph community laboratory to run through a variety of tests with different memory allocator configurations.  I've since written the results of those tests up in pdf form for folks who are interested.

The results are located here:

http://nhm.ceph.com/hackathon/Ceph_Hackathon_Memory_Allocator_Testing.pdf

I want to be clear that many other folks have done the heavy lifting here.  These results are simply a validation of the many tests that other folks have already done.  Many thanks to Sandisk and others for figuring this out as it's a pretty big deal!

Side note:  Very little tuning other than swapping the memory allocator and a couple of quick and dirty ceph tunables were set during these tests. It's quite possible that higher IOPS will be achieved as we really start digging into the cluster and learning what the bottlenecks are.

Thanks,
Mark
--
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

________________________________

PLEASE NOTE: The information contained in this electronic mail message is intended only for the use of the designated recipient(s) named above. If the reader of this message is not the intended recipient, you are hereby notified that you have received this message in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify the sender by telephone or e-mail (as shown above) immediately and destroy any and all copies of this message in your possession (whether hard copies or electronically stored copies).


  parent reply	other threads:[~2015-08-19  5:52 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19  4:45 Ceph Hackathon: More Memory Allocator Testing Mark Nelson
2015-08-19  5:13 ` Shinobu Kinjo
2015-08-19  5:36 ` Somnath Roy [this message]
2015-08-19  8:07   ` Haomai Wang
2015-08-19  9:06     ` Shinobu Kinjo
2015-08-19 12:17     ` Mark Nelson
2015-08-19 12:36       ` Dałek, Piotr
2015-08-19 12:44         ` Mark Nelson
2015-08-19 12:47           ` Dałek, Piotr
2015-08-19 12:10   ` Mark Nelson
2015-08-19  6:33 ` Stefan Priebe - Profihost AG
2015-08-19 12:20   ` Mark Nelson
2015-08-19 14:01 ` Alexandre DERUMIER
2015-08-19 16:05   ` Alexandre DERUMIER
2015-08-19 16:27     ` Somnath Roy
2015-08-19 16:55       ` Alexandre DERUMIER
2015-08-19 16:57         ` Blinick, Stephen L
2015-08-20  6:35           ` Dałek, Piotr
2015-08-20  7:08             ` Haomai Wang
2015-08-20  7:18               ` Dałek, Piotr
2015-08-19 17:29         ` Somnath Roy
2015-08-19 18:20           ` Allen Samuels
2015-08-19 18:36             ` Mark Nelson
2015-08-19 18:47               ` Łukasz Redynk
2015-08-20  6:25             ` Dałek, Piotr
2015-08-19 18:47           ` Alexandre DERUMIER
2015-08-20  1:09             ` Blinick, Stephen L
2015-08-20  2:00               ` Shinobu Kinjo
2015-08-20  5:29                 ` Alexandre DERUMIER
2015-08-20  8:17                   ` Alexandre DERUMIER
2015-08-20 12:54                     ` Shinobu Kinjo
2015-08-20 14:46                       ` Matt Benjamin
2015-08-19 20:16   ` Somnath Roy
2015-08-19 20:17     ` Stefan Priebe
2015-08-19 20:29       ` Somnath Roy
2015-08-19 20:31         ` Stefan Priebe
2015-08-19 20:34           ` Somnath Roy
2015-08-19 20:40             ` Stefan Priebe
2015-08-19 20:44               ` Somnath Roy
2015-08-21  3:45                 ` Shishir Gowda
2015-08-21  4:22                 ` Shishir Gowda
2015-08-21 14:26                   ` Milosz Tanski
2015-08-21 19:07                     ` Robert LeBlanc
2015-08-22 13:52                       ` Sage Weil
2015-08-22 13:55                     ` Sage Weil
2015-08-22 16:15                       ` Somnath Roy
2015-08-22 16:57                         ` Alexandre DERUMIER
2015-08-22 17:03                           ` Somnath Roy
2015-08-23 13:12                             ` Alexandre DERUMIER
2015-08-23 16:38                               ` Somnath Roy
2015-09-03  9:13                             ` Shinobu Kinjo
2015-09-03 13:06                               ` Daniel Gryniewicz
2015-09-03 13:12                                 ` Matt Benjamin
2015-08-24 17:01                       ` Robert LeBlanc
2015-08-19 20:50 ` Zhang, Jian

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=755F6B91B3BE364F9BCA11EA3F9E0C6F2CE1171B@SACMBXIP01.sdcorp.global.sandisk.com \
    --to=somnath.roy@sandisk.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=mnelson@redhat.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.