From: "H.J. Lu" <hjl.tools@gmail.com>
To: Sunil Pandey <skpgkp2@gmail.com>
Cc: abush wang <abushwangs@gmail.com>,
Noah Goldstein <goldstein.w.n@gmail.com>,
abushwang via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: x86-64: strlen-evex performance performance degradation compared to strlen-avx2
Date: Sun, 28 Apr 2024 09:16:42 -0700 [thread overview]
Message-ID: <CAMe9rOrA87o1eT7L1WeKR_KD5_w=VxEr1MseprgAuO5s6VdXEg@mail.gmail.com> (raw)
In-Reply-To: <CAMAf5_cDFEg__3a1ZT4zC864WurO0dPnBP2o427nbbfjeNZQDg@mail.gmail.com>
On Sun, Apr 28, 2024 at 9:13 AM Sunil Pandey <skpgkp2@gmail.com> wrote:
>
>
>
> On Sat, Apr 27, 2024 at 7:13 PM abush wang <abushwangs@gmail.com> wrote:
>>
>> Actually, I was handling performance issue from libmicro in our distro OS.
>> I found that the performance degradation of localtime_r benchmark from libmicro is blame to strlen.
>> So I abstracted this test case.
>>
>
> Can you consistently reproduce strlen perf behaviour by running multiple times back-to-back?
>
> You can see high swing from run
Hi Sunil,
Intel(R) Xeon(R) Gold 6133 CPU @ 2.50GHz is SKX. Please add this test to
benchtests/bench-strlen.c and check its performance on SKX.
--
H.J.
next prev parent reply other threads:[~2024-04-28 16:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 4:03 x86-64: strlen-evex performance performance degradation compared to strlen-avx2 abush wang
2024-04-26 13:30 ` H.J. Lu
2024-04-26 16:53 ` Sunil Pandey
2024-04-28 2:13 ` abush wang
2024-04-28 16:12 ` Sunil Pandey
2024-04-28 16:16 ` H.J. Lu [this message]
2024-04-29 17:41 ` Sunil Pandey
2024-04-29 20:19 ` H.J. Lu
2024-04-30 0:54 ` Sunil Pandey
2024-04-30 2:51 ` H.J. Lu
2024-04-30 20:16 ` Sunil Pandey
2024-04-28 2:06 ` abush wang
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMe9rOrA87o1eT7L1WeKR_KD5_w=VxEr1MseprgAuO5s6VdXEg@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=abushwangs@gmail.com \
--cc=goldstein.w.n@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=skpgkp2@gmail.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 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).