From: Alexandre DERUMIER <aderumier@odiso.com>
To: Mark Nelson <mnelson@redhat.com>
Cc: Blair Bethwaite <blair.bethwaite@gmail.com>,
James Page <james.page@ubuntu.com>,
ceph-devel <ceph-devel@vger.kernel.org>,
Stephen L Blinick <stephen.l.blinick@intel.com>,
Jay Vosburgh <jay.vosburgh@canonical.com>,
Colin Ian King <colin.king@canonical.com>,
Patricia Gaughen <patricia.gaughen@canonical.com>,
Leann Ogasawara <leann.ogasawara@canonical.com>
Subject: Re: Memstore performance improvements v0.90 vs v0.87
Date: Sat, 21 Feb 2015 10:02:53 +0100 (CET) [thread overview]
Message-ID: <1725252187.1574758.1424509373883.JavaMail.zimbra@oxygem.tv> (raw)
In-Reply-To: <1429598219.1574757.1424509359439.JavaMail.zimbra@oxygem.tv>
>>One Other thing you could also check, is if transparent hugepages is enabled or not.
>>It's known to slowdown some applications, like databases for example. (So maybe memstore too)
>>
>>#cat /sys/kernel/mm/transparent_hugepage/enabled
>> always madvise [never]
This is disabled by default is you use the network-latency tuned profile
https://developerblog.redhat.com/2015/02/11/low-latency-performance-tuning-rhel-7/
----- Mail original -----
De: "aderumier" <aderumier@odiso.com>
À: "Mark Nelson" <mnelson@redhat.com>
Cc: "Blair Bethwaite" <blair.bethwaite@gmail.com>, "James Page" <james.page@ubuntu.com>, "ceph-devel" <ceph-devel@vger.kernel.org>, "Stephen L Blinick" <stephen.l.blinick@intel.com>, "Jay Vosburgh" <jay.vosburgh@canonical.com>, "Colin Ian King" <colin.king@canonical.com>, "Patricia Gaughen" <patricia.gaughen@canonical.com>, "Leann Ogasawara" <leann.ogasawara@canonical.com>
Envoyé: Samedi 21 Février 2015 09:10:29
Objet: Re: Memstore performance improvements v0.90 vs v0.87
>>At least at first glance it doesn't look like it's enabled on either our
>>RHEL7 or Ubuntu nodes. No numad running either.
Do you have disable autonuma balancing manually ?
because look at kernel config of both rhel7 and ubuntu, it's really seem to be enabled by default:
CONFIG_ARCH_SUPPORTS_NUMA_BALANCING=y
CONFIG_NUMA_BALANCING_DEFAULT_ENABLED=y
CONFIG_NUMA_BALANCING=y
>>No numad running either.
AFAIK, numad was used by RHEL6, and auto-numabalancing is used since RHEL7.
One Other thing you could also check, is if transparent hugepages is enabled or not.
It's known to slowdown some applications, like databases for example. (So maybe memstore too)
#cat /sys/kernel/mm/transparent_hugepage/enabled
always madvise [never]
----- Mail original -----
De: "Mark Nelson" <mnelson@redhat.com>
À: "aderumier" <aderumier@odiso.com>
Cc: "Blair Bethwaite" <blair.bethwaite@gmail.com>, "James Page" <james.page@ubuntu.com>, "ceph-devel" <ceph-devel@vger.kernel.org>, "Stephen L Blinick" <stephen.l.blinick@intel.com>, "Jay Vosburgh" <jay.vosburgh@canonical.com>, "Colin Ian King" <colin.king@canonical.com>, "Patricia Gaughen" <patricia.gaughen@canonical.com>, "Leann Ogasawara" <leann.ogasawara@canonical.com>
Envoyé: Vendredi 20 Février 2015 17:12:46
Objet: Re: Memstore performance improvements v0.90 vs v0.87
On 02/20/2015 10:03 AM, Alexandre DERUMIER wrote:
>>> http://rhelblog.redhat.com/2015/01/12/mysteries-of-numa-memory-management-revealed/
>>> It's possible that this could be having an effect on the results.
>
> Isn't auto numa balancing enabled by default since kernel 3.8 ?
No idea, I'm behind the times on what's been going on with numa tuning.
>
> it can be checked with
>
> cat /proc/sys/kernel/numa_balancing
At least at first glance it doesn't look like it's enabled on either our
RHEL7 or Ubuntu nodes. No numad running either.
--
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
--
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:[~2015-02-21 9:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 7:05 Memstore performance improvements v0.90 vs v0.87 Blinick, Stephen L
2015-01-14 22:32 ` Blinick, Stephen L
2015-01-14 22:43 ` Mark Nelson
2015-01-14 23:39 ` Blinick, Stephen L
2015-01-27 21:03 ` Mark Nelson
2015-01-28 1:23 ` Blinick, Stephen L
2015-01-28 21:51 ` Mark Nelson
2015-01-29 12:51 ` James Page
2015-02-20 9:07 ` James Page
2015-02-20 9:49 ` Blair Bethwaite
2015-02-20 10:09 ` Haomai Wang
2015-02-20 15:38 ` Mark Nelson
[not found] ` <524687337.1545267.1424448115086.JavaMail.zimbra@oxygem.tv>
2015-02-20 16:03 ` Alexandre DERUMIER
2015-02-20 16:12 ` Mark Nelson
[not found] ` <298703592.1573873.1424506210041.JavaMail.zimbra@oxygem.tv>
2015-02-21 8:10 ` Alexandre DERUMIER
[not found] ` <1429598219.1574757.1424509359439.JavaMail.zimbra@oxygem.tv>
2015-02-21 9:02 ` Alexandre DERUMIER [this message]
2015-02-20 18:38 ` Stefan Priebe
2015-02-20 15:51 ` Mark Nelson
2015-02-20 15:58 ` James Page
2015-01-14 22:44 ` Somnath Roy
2015-01-14 23:37 ` Blinick, Stephen L
2015-01-15 10:43 ` Andreas Bluemle
2015-01-15 17:09 ` Sage Weil
2015-01-15 17:15 ` Sage Weil
2015-01-19 9:28 ` Andreas Bluemle
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=1725252187.1574758.1424509373883.JavaMail.zimbra@oxygem.tv \
--to=aderumier@odiso.com \
--cc=blair.bethwaite@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=colin.king@canonical.com \
--cc=james.page@ubuntu.com \
--cc=jay.vosburgh@canonical.com \
--cc=leann.ogasawara@canonical.com \
--cc=mnelson@redhat.com \
--cc=patricia.gaughen@canonical.com \
--cc=stephen.l.blinick@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.