public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "adhemerval.zanella at linaro dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/27651] Performance regression after updating to 2.33
Date: Mon, 29 Mar 2021 12:36:10 +0000 [thread overview]
Message-ID: <bug-27651-131-ajkDZdKBbF@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27651-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27651
--- Comment #3 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
The performance profile can be obtained by the 'perf' tool [1], which is
supported and distributed by mostly of the distributions (it is a kernel
project hosted within the linux kernel).
The most simple usage is the record/report, where you issue:
$ perf record <program>
$ perf report --stdio
The first command will generate a large file containing the performance data
obtained by the kernel while the second will parse and dump to console a perf
per sybmol cpu cycles spent (the default counter).
Doing it with both glibc 2.32 and glibc 2.33 we can have an idea of what is
happening.
My wild guess is maybe something related to a memory routine selection, I need
to check if something has changed on x86_64 side regarding it.
[1] https://perf.wiki.kernel.org/index.php/Main_Page
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-29 12:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 22:17 [Bug libc/27651] New: " rcd99 at zipmail dot com.br
2021-03-26 13:45 ` [Bug libc/27651] " adhemerval.zanella at linaro dot org
2021-03-27 0:58 ` rcd99 at zipmail dot com.br
2021-03-29 12:36 ` adhemerval.zanella at linaro dot org [this message]
2021-03-30 9:13 ` rcd99 at zipmail dot com.br
2021-03-30 9:42 ` rcd99 at zipmail dot com.br
2021-03-30 21:08 ` adhemerval.zanella at linaro dot org
2021-03-31 8:56 ` rcd99 at zipmail dot com.br
2021-03-31 12:32 ` adhemerval.zanella at linaro dot org
2021-03-31 20:42 ` rcd99 at zipmail dot com.br
2021-03-31 20:46 ` adhemerval.zanella at linaro dot org
2021-03-31 23:16 ` rcd99 at zipmail dot com.br
2021-04-01 19:12 ` adhemerval.zanella at linaro dot org
2021-04-01 20:42 ` rcd99 at zipmail dot com.br
2021-04-01 20:42 ` rcd99 at zipmail dot com.br
2021-04-12 22:01 ` cvs-commit at gcc dot gnu.org
2021-04-13 13:11 ` adhemerval.zanella at linaro dot org
2021-04-13 13:13 ` adhemerval.zanella at linaro dot org
2021-04-13 13:30 ` schwab@linux-m68k.org
2021-04-13 21:03 ` cvs-commit at gcc dot gnu.org
2021-04-28 10:21 ` fweimer at redhat dot com
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-27651-131-ajkDZdKBbF@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).