All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Nelson <mnelson@redhat.com>
To: "\"Dałek, Piotr\"" <Piotr.Dalek@ts.fujitsu.com>,
	"Mark Nelson" <mark.a.nelson@gmail.com>,
	ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Follow-Up on Alexandre's Transparent Huge Pages Testing
Date: Tue, 29 Sep 2015 08:22:18 -0500	[thread overview]
Message-ID: <560A908A.9040208@redhat.com> (raw)
In-Reply-To: <90559C83A9C7FA45B5846C975DFA612DDB54D32F42@ABGEX73E.FSC.NET>



On 09/29/2015 12:59 AM, Dałek, Piotr wrote:
>> -----Original Message-----
>> From: ceph-devel-owner@vger.kernel.org [mailto:ceph-devel-
>> owner@vger.kernel.org] On Behalf Of Mark Nelson
>> Sent: Tuesday, September 29, 2015 1:34 AM
>>
>> Hi Everyone,
>>
>> A while back Alexandre Derumier posted some test results looking at how
>> transparent huge pages can reduce memory usage with jemalloc.  I went
>> back and ran a number of new tests on the community performance cluster
>> to verify his findings and also look at how performance and cpu usage were
>> affected, both during various fio benchmark tests and also during a 4k
>> random write recovery scenario.  I tested tcmalloc 2.4 with 32MB thread
>> cache, 128MB thread cache, and jemalloc 4.0.
>> [..]
>> Here's are the results:
>>
>> https://drive.google.com/file/d/0B2gTBZrkrnpZY3U3TUU3RkJVeVk/view
>
>  From my point of view, this looks excellent. I generally didn't like the idea of moving to Jemalloc because of memory usage increase (which is absurdly high as you can see from the graphs), but with THP disabled things look way better.
> How about trying Jemalloc 4 without THP and with Ceph patched with https://github.com/ceph/ceph/pull/5855? I wonder how much difference it'll give on Incerta.

I actually did try 5855, but there was a nasty monitor memory leak in 
master that prevented the tests from running.  It didn't get fixed until 
early last week and 5855 no longer merges cleanly with latest master.  I 
haven't had time to go back and see what's conflicting, but if you want 
to take a look and update it I would be happy to give it a whirl. :)

Mark

>
>
> With best regards / Pozdrawiam
> Piotr Dałek
>
>
> N�����r��y���b�X��ǧv�^�)޺{.n�+���z�]z���{ay�\x1dʇڙ�,j\a��f���h���z�\x1e�w���\f���j:+v���w�j�m����\a����zZ+�����ݢj"��!tml=
>
--
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

  reply	other threads:[~2015-09-29 13:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-28 23:33 Follow-Up on Alexandre's Transparent Huge Pages Testing Mark Nelson
2015-09-29  5:59 ` Dałek, Piotr
2015-09-29 13:22   ` Mark Nelson [this message]
2015-09-29 14:28     ` Dałek, Piotr

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=560A908A.9040208@redhat.com \
    --to=mnelson@redhat.com \
    --cc=Piotr.Dalek@ts.fujitsu.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=mark.a.nelson@gmail.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.