public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "xuchunmei at linux dot alibaba.com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug math/27461] Unixbench/whetstone-double performance regression on glibc2.32 Date: Tue, 02 Mar 2021 04:59:28 +0000 [thread overview] Message-ID: <bug-27461-131-bzxANSBkVX@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27461-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27461 --- Comment #4 from xuchunmei <xuchunmei at linux dot alibaba.com> --- I tested on another x86 cpu without fma, the hot function is __ieee754_exp_avx and __ieee754_log_avx, the result shows that glibc2.32 is a little better than glibc2.28. on glibc2.32: Benchmark Run: Tue Mar 02 2021 12:51:38 - 12:51:55 8 CPUs in system; running 8 parallel copies of tests Double-Precision Whetstone 28050.2 MWIPS (10.0 s, 1 samples) System Benchmarks Partial Index BASELINE RESULT INDEX Double-Precision Whetstone 55.0 28050.2 5100.0 ======== System Benchmarks Index Score (Partial Only) 5100.0 on glibc2.28: Benchmark Run: Tue Mar 02 2021 12:53:01 - 12:53:19 8 CPUs in system; running 8 parallel copies of tests Double-Precision Whetstone 27715.3 MWIPS (9.5 s, 1 samples) System Benchmarks Partial Index BASELINE RESULT INDEX Double-Precision Whetstone 55.0 27715.3 5039.2 ======== System Benchmarks Index Score (Partial Only) 5039.2 perf data: glibc2.32: + 53.99% whetstone-doubl whetstone-double [.] whetstones.constprop.1 + 13.42% whetstone-doubl libm-2.32.so [.] __atan_avx + 9.95% whetstone-doubl libm-2.32.so [.] __cos_avx + 7.03% whetstone-doubl libm-2.32.so [.] __ieee754_log_avx + 6.86% whetstone-doubl libm-2.32.so [.] __ieee754_exp_avx + 6.44% whetstone-doubl libm-2.32.so [.] __sincos + 1.13% whetstone-doubl libm-2.32.so [.] exp@@GLIBC_2.29 0.31% whetstone-doubl libm-2.32.so [.] log@@GLIBC_2.29 0.22% whetstone-doubl [kernel.kallsyms] [k] __softirqentry_text_start 0.15% whetstone-doubl whetstone-double [.] log@plt 0.11% whetstone-doubl libm-2.32.so [.] 0x000000000000f3a4 0.05% whetstone-doubl whetstone-double [.] sincos@plt 0.03% whetstone-doubl whetstone-double [.] exp@plt 0.02% whetstone-doubl [kernel.kallsyms] [k] run_timer_softirq 0.01% whetstone-doubl whetstone-double [.] cos@plt 0.01% whetstone-doubl whetstone-double [.] atan@plt 0.01% whetstone-doubl [kernel.kallsyms] [k] finish_task_switch glibc2.28: + 52.14% whetstone-doubl whetstone-double [.] whetstones.constprop.1 + 12.88% whetstone-doubl libm-2.28.so [.] __atan_avx + 12.64% whetstone-doubl libm-2.28.so [.] __ieee754_log_avx + 9.85% whetstone-doubl libm-2.28.so [.] __cos_avx + 6.43% whetstone-doubl libm-2.28.so [.] __sincos + 5.32% whetstone-doubl libm-2.28.so [.] __ieee754_exp_avx 0.14% whetstone-doubl whetstone-double [.] __log_finite@plt 0.14% whetstone-doubl whetstone-double [.] __exp_finite@plt 0.12% whetstone-doubl [kernel.kallsyms] [k] __softirqentry_text_start 0.05% whetstone-doubl whetstone-double [.] sincos@plt 0.01% whetstone-doubl [kernel.kallsyms] [k] run_timer_softirq 0.01% whetstone-doubl [kernel.kallsyms] [k] _raw_spin_unlock_irqrestore cpuinfo: # lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 2 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 45 Model name: Intel(R) Xeon(R) CPU E5-2430 0 @ 2.20GHz Stepping: 7 CPU MHz: 2194.710 BogoMIPS: 4389.42 Virtualization: VT-x Hypervisor vendor: KVM Virtualization type: full L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 15360K NUMA node0 CPU(s): 0-7 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl cpuid tsc_known_freq pni pclmulqdq vmx ssse3 cx16 pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx hypervisor lahf_lm cpuid_fault ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid tsc_adjust xsaveopt -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2021-03-02 4:59 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-24 4:57 [Bug math/27461] New: " xuchunmei at linux dot alibaba.com 2021-02-24 4:58 ` [Bug math/27461] " xuchunmei at linux dot alibaba.com 2021-02-24 4:59 ` xuchunmei at linux dot alibaba.com 2021-02-24 5:36 ` siddhesh at sourceware dot org 2021-02-24 9:45 ` nsz at gcc dot gnu.org 2021-02-24 10:49 ` wdijkstr at arm dot com 2021-02-25 11:04 ` xuchunmei at linux dot alibaba.com 2021-03-01 12:06 ` xuchunmei at linux dot alibaba.com 2021-03-02 4:59 ` xuchunmei at linux dot alibaba.com [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=bug-27461-131-bzxANSBkVX@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: linkBe 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).