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/25860] stress-ng tsearch regressed ~14% with upgrade glibc from 2.29 to 2.30
Date: Tue, 28 Apr 2020 13:04:18 +0000 [thread overview]
Message-ID: <bug-25860-131-LQ2MZgpsan@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25860-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25860
Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |adhemerval.zanella at linaro dot o
| |rg
--- Comment #3 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
The stress-ng from phoronix-test-suite has multiple options that stress
different implementations:
Stress-NG 0.11.07:
pts/stress-ng-1.3.0
System Test Configuration
1: CPU Stress
2: Crypto
3: Memory Copying
4: Glibc Qsort Data Sorting
5: Glibc C String Functions
6: Vector Math
7: Matrix Math
8: Forking
9: System V Message Passing
10: Semaphores
11: Socket Activity
12: Context Switching
13: Atomic
14: CPU Cache
15: Malloc
16: MEMFD
17: MMAP
18: NUMA
19: RdRand
20: SENDFILE
Which one are you seeing regressions and with a profiling which glibc symbols
does it stress?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-04-28 13:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 2:59 [Bug libc/25860] New: " yu.ma at intel dot com
2020-04-21 3:00 ` [Bug libc/25860] " yu.ma at intel dot com
2020-04-21 9:53 ` fw at deneb dot enyo.de
2020-04-21 9:54 ` fw at deneb dot enyo.de
2020-04-28 6:15 ` yu.ma at intel dot com
2020-04-28 13:04 ` adhemerval.zanella at linaro dot org [this message]
2020-04-29 0:40 ` yu.ma at intel dot com
2020-04-29 16:23 ` adhemerval.zanella at linaro dot org
2020-04-30 5:41 ` yu.ma at intel dot com
2020-05-04 6:56 ` fw at deneb dot enyo.de
2023-10-31 17:40 ` adhemerval.zanella at linaro 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-25860-131-LQ2MZgpsan@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).