public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "yangyanchao6 at huawei dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug malloc/29296] New: tpcc-mysql scores decreased by about 11.2% at glibc-2.36
Date: Wed, 29 Jun 2022 06:45:26 +0000 [thread overview]
Message-ID: <bug-29296-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29296
Bug ID: 29296
Summary: tpcc-mysql scores decreased by about 11.2% at
glibc-2.36
Product: glibc
Version: 2.36
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: malloc
Assignee: unassigned at sourceware dot org
Reporter: yangyanchao6 at huawei dot com
Target Milestone: ---
At Kunpeng920 platform, tpcc-mysql scores decreased by about 11.2% between
glibc-2.36 and glibc2.28 with mysql-8.0.20.
Comparing the code, I find that the two commits causes performance degradation.
11a02b035b46 (misc: Add __get_nprocs_sched)
97ba273b5057 (linux: __get_nprocs_sched: do not feed CPU_COUNT_S with
garbage [BZ #28850])
These two patches modify the default behavior.
Another message is that my machine is 96 cores and I have 91 core bindings for
tpcc-mysql.
This means that perhaps the current approach to computing arenas is not optimal
in the case of core binding.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-06-29 6:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 6:45 yangyanchao6 at huawei dot com [this message]
2022-06-29 6:47 ` [Bug malloc/29296] " yangyanchao6 at huawei dot com
2023-10-11 16:11 ` adhemerval.zanella at linaro dot org
2023-10-12 2:31 ` sam at gentoo dot org
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=bug-29296-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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).