Below is the same benchmark from the case description, validating the
performance regression on Groovy. Patched glibc builds for both Focal
and Groovy amd64/i386 are available at ppa:halves/lp1928508-test [0].
$ hyperfine -n groovy-2.32-0ubuntu3 'lxc exec groovy ./test_memcpy64 32' -n
groovy-patched 'lxc exec groovy-patched ./test_memcpy64 32'
Benchmark #1: groovy-2.32-0ubuntu3
Time (mean ± σ): 2.392 s ± 0.039 s [User: 4.8 ms, System: 5.4 ms]
Range (min … max): 2.366 s … 2.494 s 10 runs
Benchmark #2: groovy-patched
Time (mean ± σ): 1.381 s ± 0.010 s [User: 6.1 ms, System: 4.3 ms]
Range (min … max): 1.372 s … 1.407 s 10 runs
Summary
'groovy-patched' ran
1.73 ± 0.03 times faster than 'groovy-2.32-0ubuntu3'
$ head -n5 /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 23
model : 113
model name : AMD Ryzen 7 3700X 8-Core Processor
[0] https://launchpad.net/~halves/+archive/ubuntu/lp1928508-test
** Changed in: glibc (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: glibc (Ubuntu Groovy)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928508
Title:
Performance regression on memcpy() calls for AMD Zen
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1928508/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
