All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Nelson <mnelson@redhat.com>
To: ceph-devel <ceph-devel@vger.kernel.org>
Cc: "ceph-users@lists.ceph.com" <ceph-users@lists.ceph.com>
Subject: Initial performance cluster SimpleMessenger vs AsyncMessenger results
Date: Mon, 12 Oct 2015 11:50:43 -0500	[thread overview]
Message-ID: <561BE4E3.7050404@redhat.com> (raw)

Hi Guy,

Given all of the recent data on how different memory allocator 
configurations improve SimpleMessenger performance (and the effect of 
memory allocators and transparent hugepages on RSS memory usage), I 
thought I'd run some tests looking how AsyncMessenger does in 
comparison.  We spoke about these a bit at the last performance meeting 
but here's the full write up.  The rough conclusion as of right now 
appears to be:

1) AsyncMessenger performance is not dependent on the memory allocator 
like with SimpleMessenger.

2) AsyncMessenger is faster than SimpleMessenger with TCMalloc + 32MB 
(ie default) thread cache.

3) AsyncMessenger is consistently faster than SimpleMessenger for 128K 
random reads.

4) AsyncMessenger is sometimes slower than SimpleMessenger when memory 
allocator optimizations are used.

5) AsyncMessenger currently uses far more RSS memory than SimpleMessenger.

Here's a link to the paper:

https://drive.google.com/file/d/0B2gTBZrkrnpZS1Q4VktjZkhrNHc/view

Mark

             reply	other threads:[~2015-10-12 16:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-12 16:50 Mark Nelson [this message]
     [not found] ` <561BE4E3.7050404-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-10-13  2:56   ` Initial performance cluster SimpleMessenger vs AsyncMessenger results Haomai Wang
2015-10-13  2:56     ` [ceph-users] " Haomai Wang
     [not found]       ` <CACJqLyY+11d9ENxnMeNSTnJ-u-CAKbEED79GAjgJU7=nAAZ=9A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-13 12:58         ` Sage Weil
2015-10-13 13:03       ` [ceph-users] " Mark Nelson
     [not found]         ` <561D0113.108-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-10-14 15:57           ` Chen, Xiaoxi
2015-10-14 16:54             ` [ceph-users] " Mark Nelson
     [not found]     ` <CACJqLyaF-rtPVe2cX=y19cxcupfWPVXeZSpgpofXxR1qktwo2g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-13  4:18       ` Somnath Roy
2015-10-13  6:34         ` [ceph-users] " Haomai Wang
2015-10-13  6:45           ` Somnath Roy
2015-10-13  6:48             ` Haomai Wang
2015-10-13  7:20             ` Dałek, Piotr
2015-10-13  4:12   ` Gregory Farnum
2015-10-13 15:52     ` Mark Nelson

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=561BE4E3.7050404@redhat.com \
    --to=mnelson@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=ceph-users@lists.ceph.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.