From: Mark Nelson <mark.a.nelson@gmail.com>
To: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Follow-Up on Alexandre's Transparent Huge Pages Testing
Date: Mon, 28 Sep 2015 18:33:32 -0500 [thread overview]
Message-ID: <5609CE4C.5060403@gmail.com> (raw)
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.
The gist of it is that I also see a reduction in memory usage, most
pronounced with jemalloc. Unfortuantely the best reduction in memory
usage is when memory usage is already fairly low. The most important
case is the memory spike when OSDs are marked back up/in during a
recovery test. In this case there is still a benefit, though memory
usage is still a little higher than TCMalloc with 128MB thread cache.
There's a little bit of a concerning trend where memory usage appears to
increase fairly quickly after the recovery test is complete and the
post-recovery phase of the benchmark is running. That will likely need
to be investigate in more depth.
I have been doing some other tests with the async messenger and
newstore, but those will have to wait for another paper.
Here's are the results:
https://drive.google.com/file/d/0B2gTBZrkrnpZY3U3TUU3RkJVeVk/view
Mark
next reply other threads:[~2015-09-28 23:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 23:33 Mark Nelson [this message]
2015-09-29 5:59 ` Follow-Up on Alexandre's Transparent Huge Pages Testing Dałek, Piotr
2015-09-29 13:22 ` Mark Nelson
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=5609CE4C.5060403@gmail.com \
--to=mark.a.nelson@gmail.com \
--cc=ceph-devel@vger.kernel.org \
/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.