From: Yang Yanchao <yangyanchao6@huawei.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>,
Qingqing Li <liqingqing3@huawei.com>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
DJ Delorie <dj@redhat.com>
Cc: "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
<ldv@altlinux.org>, <linfeilong@huawei.com>
Subject: Re: [PATCH] malloc: Optimize the number of arenas for better application performance [BZ# 29296]
Date: Wed, 29 Jun 2022 16:05:42 +0800 [thread overview]
Message-ID: <61510381-60ad-1af7-b683-4b8e17f20c88@huawei.com> (raw)
In-Reply-To: <3a29fd54-aece-b79e-7e63-33e2882d1f90@gotplt.org>
On 2022/6/29 13:25, Siddhesh Poyarekar wrote:
> I'm not strongly opposed to reverting (see above for more nuance) but
> would like us to use this opportunity to at least track a project to
> improve the arenas heuristic. Could you or Adhemerval please add a bug
> report on sourceware to study the performance impact of arena counts and
> their relationship to core counts on different architectures/systems?
Thanks to the attention paid to this issue, I created a bug report on
sourceware(https://sourceware.org/bugzilla/show_bug.cgi?id=29296).
Based on the openEuler 2203 LTS, we tested in different application
scenarios(ceph, Hbase, Hibench, spark sql, hive sql). Only tpcc-mysql
has this performance degradation because only tpcc-mysql has core
binding configured.
I'm using different arena counts and their relationship to core counts,
based on x86_64 and aarch64. tpcc-mysql tests are slow to run and will
take several days.
prev parent reply other threads:[~2022-06-29 8:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 9:40 malloc: Optimize the number of arenas for better application performance Yang Yanchao
2022-06-28 11:18 ` Florian Weimer
2022-06-28 12:38 ` Siddhesh Poyarekar
2022-06-28 13:35 ` Adhemerval Zanella
2022-06-28 18:56 ` DJ Delorie
2022-06-28 19:17 ` Adhemerval Zanella
[not found] ` <1a8f10e034e7489c8e9f090e9c90b396@huawei.com>
2022-06-29 2:37 ` 转发: " Qingqing Li
2022-06-29 5:25 ` Siddhesh Poyarekar
2022-06-29 8:05 ` Yang Yanchao [this message]
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=61510381-60ad-1af7-b683-4b8e17f20c88@huawei.com \
--to=yangyanchao6@huawei.com \
--cc=adhemerval.zanella@linaro.org \
--cc=dj@redhat.com \
--cc=ldv@altlinux.org \
--cc=libc-alpha@sourceware.org \
--cc=linfeilong@huawei.com \
--cc=liqingqing3@huawei.com \
--cc=siddhesh@gotplt.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).