This bug was fixed in the package glibc - 2.31-0ubuntu9.9
---
glibc (2.31-0ubuntu9.9) focal; urgency=medium
* Disable testsuite on riscv64. It is failing maths tests intermittently in
ways that cannot be a glibc regression and is disabled in later series
anyway.
glibc
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951032
Title:
AArch64:
2.31-0ubuntu9.7 vs 2.31-0ubuntu9.9
= X-Gene =
length | before (MiB/s) | after (MiB/s) |delta
--|||--
32768 | 122.27 | 122.26 | -0.00%
65536 | 216.55 | 215.81 | -0.34%
131072 | 321.97 |
Ran the tests against -updates and -proposed on a Pi 4, Pi 3B+, and Pi
Zero 2 with the following results:
= Raspberry Pi 4 =
length | before (MiB/s) | after (MiB/s) |delta
--|||--
32768 | 83.58 | 83.03 | -0.66%
I ran the tests on a graviton2 instance and saw the improvement as
expected/desired:
length | before (MiB/s) | after (MiB/s) |delta
--|||--
32768 | 233.19 | 247.61 |6.18%
65536 | 443.44 | 468.68 |
Dave, if you have time to test 2.31-0ubuntu9.8~ppa4 vs focal-update that
would be interesting -- I think given Dann's results though they will be
pretty neutral though so I wouldn't worry over much about it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On the performance regression on the Pi 0/3 models above, bear in mind
that the models showing the regression are all the models with <=1GB of
RAM. Assuming there's no regression on the armhf side of things (I
haven't tested this, but I got the impression this was an arm64 only
change?), we
Results for the 2.31-0ubuntu9.8~ppa3 build:
= X-Gene =
length | before (MiB/s) | after (MiB/s) |delta
--|||--
32768 | 122.23 | 122.24 |0.01%
65536 | 215.55 | 215.23 | -0.15%
131072 |
Results for the 2.31-0ubuntu9.8~ppa2 build:
= X-Gene =
length | before (MiB/s) | after (MiB/s) |delta
--|||--
32768 | 122.20 | 122.20 |0.00%
65536 | 215.42 | 213.49 | -0.89%
131072 |
Some more results:
= Raspberry Pi 3B 1GB =
length | before (MiB/s) | after (MiB/s) |delta
--|||--
32768 | 48.24 | 46.19 | -4.26%
65536 | 85.99 | 79.96 | -7.02%
131072 | 154.00 |
= Raspberry Pi 4B (rev 1.1) 4GB =
length | before (MiB/s) | after (MiB/s) |delta
--|||--
32768 | 83.88 | 84.21 |0.39%
65536 | 156.15 | 158.85 |1.73%
131072 | 292.38 |
= ThunderX2 =
length | before (MiB/s) | after (MiB/s) |delta
--|||--
32768 | 126.67 | 115.21 | -9.05%
65536 | 267.91 | 244.92 | -8.58%
131072 | 510.48 | 473.60 | -7.22%
It was pointed out to me that my compare.py script printed the times the
wrong way around, so I fixed that and also changed it to print output in
MiB/s -- always easier to reason about a benchmark when "bigger is
better"!
** Description changed:
[impact]
glibc 2.32 contained a number of
** Description changed:
[impact]
glibc 2.32 contained a number of improvements to the memcpy routines for
server-grade AArch64 implementations (in particular, graviton2 & graviton3).
They should be backported to focal, as the LTS releases are by far the most
used on servers.
[test
Here's a set of regression tests I ran across various ARM Server SoCs:
https://docs.google.com/spreadsheets/d/1hSdI5XKgXXw2iKV1Ceab0w3kqaO8wcO_cwYKQn0cdwA/edit#gid=0
This does show a negative performance impact for all but 1, the worst
one being just over 2% (Altra).
--
You received this bug
Bumping up the buffer sizes mentioned in [Test Case] from 32 -> 1024. In
my testing, 32 results are inconsistent, perhaps due to caching effects.
1024 results look far more reliable.
** Description changed:
[impact]
glibc 2.32 contained a number of improvements to the memcpy routines for
Here's a version that compiles on arm64. Do note it expects a command
line argument, the size of the buffer to use in megabytes.
** Attachment added: "test_memcpy.c"
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1951032/+attachment/5557684/+files/test_memcpy.c
** Description changed:
** Description changed:
[impact]
glibc 2.32 contained a number of improvements to the memcpy routines for
server-grade AArch64 implementations (in particular, graviton2 & graviton3).
They should be backported to focal, as the LTS releases are by far the most
used on servers.
[test
I attempted to regression test this on a set of arm64 server SoCs, but:
$ gcc -g -O3 test_memcpy.c -o test_memcpy64
test_memcpy.c:6:10: fatal error: mm_malloc.h: No such file or directory
6 | #include
| ^
compilation terminated.
--
You received this bug
** Changed in: glibc (Ubuntu)
Status: Invalid => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951032
Title:
AArch64: Backport memcpy improvements
To manage notifications
Hello Michael, or anyone else affected,
Accepted glibc into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/glibc/2.31-0ubuntu9.4
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
[impact]
glibc 2.32 contained a number of improvements to the memcpy routines for
server-grade AArch64 implementations (in particular, graviton2 & graviton3).
They should be backported to focal, as the LTS releases are by far the most
used on servers.
[test
** Description changed:
[impact]
glibc 2.32 contained a number of improvements to the memcpy routines for
server-grade AArch64 implementations (in particular, graviton2 & graviton3).
They should be backported to focal, as the LTS releases are by far the most
used on servers.
[test
** Changed in: glibc (Ubuntu Focal)
Status: New => 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/1951032
Title:
AArch64: Backport memcpy improvements
To manage notifications
** Description changed:
[impact]
glibc 2.32 contained a number of improvements to the memcpy routines for
server-grade AArch64 implementations (in particular, graviton2 & graviton3).
They should be backported to focal, as the LTS releases are by far the most
used on servers.
[test
25 matches
Mail list logo
