Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1276753
Summary: | malloc: arena free list can become cyclic, increasing contention | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Paulo Andrade <pandrade> |
Component: | glibc | Assignee: | Florian Weimer <fweimer> |
Status: | CLOSED ERRATA | QA Contact: | Arjun Shankar <ashankar> |
Severity: | high | Docs Contact: | Marc Muehlfeld <mmuehlfe> |
Priority: | high | ||
Version: | 7.1 | CC: | akarlsso, ashankar, a.stimec, bobby.prins, bugproxy, codonell, cww, david.linden, dsulliva, efi, eyal, fweimer, hannsj_uhl, jkachuck, ken.verma, law, mcermak, mgrf, mnewsome, pandrade, pfrankli, qe-baseos-tools-bugs, raanan, rsussman, salmy, sumeet.keswani, trinh.dao, t.williams |
Target Milestone: | rc | Keywords: | Patch |
Target Release: | 7.3 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | glibc-2.17-156.el7 | Doc Type: | Bug Fix |
Doc Text: |
Core C library (glibc) enhanced to increase *malloc()* scalability
A defect in the implementation of the *malloc()* function could result in unnecessary serialization of memory allocation requests across threads. This update fixes the bug and substantially increases the concurrent throughput of allocation requests for applications that frequently create and destroy threads.
|
Story Points: | --- |
Clone Of: | 1264189 | Environment: | |
Last Closed: | 2016-11-03 08:27:05 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1297579, 1364088 |
Comment 14
Carlos O'Donell
2016-01-11 15:08:40 UTC
*** Bug 1297423 has been marked as a duplicate of this bug. *** Note: I will make this bug public soon so that others can comment if they feel so inclined. *** Bug 1330623 has been marked as a duplicate of this bug. *** In our case (vertica database server) once the arena freelist goes circular, it affects the application moving forward independent of concurrency (as the application becomes sick). This causes significant performance degradation in high concurrency situations. We tested the efficacy of the patch posted on sourceware internally by (re)building glibc and the patch was stable and improved performance under concurrent load. A couple customers have tested it not just for stability (it is) but also for performance (it helps). What is the target release date for 7.3, thus glibc-2.17-131.el7 will be available? What are the prospects for publishing glibc-2.17-131.el7 as an update prior to 7.3? What are the prospects of backporting this to the glibc-2.12 stream for RHEL6? (In reply to Sumeet Keswani from comment #26) > In our case (vertica database server) once the arena freelist goes circular, > it affects the application moving forward independent of concurrency (as the > application becomes sick). > > This causes significant performance degradation in high concurrency > situations. > > We tested the efficacy of the patch posted on sourceware internally by > (re)building glibc and the patch was stable and improved performance under > concurrent load. > A couple customers have tested it not just for stability (it is) but also > for performance (it helps). You should see a similar performance improvement on Red Hat Enterprise Linux 6.8 Beta, where we fixed this issue as bug 1264189 (currently private). is this fix included in glibc-2.12-1.192 ? does not show up in this advisory? (RHBA-2016:0834-1) https://rhn.redhat.com/errata/RHBA-2016-0834.html How can users on RHEL 6.X get this fix? can i get access to BZ 1264189 Hello, I have requested HPE access to BZ 1264189. Please note this BZ was closed with errata: https://rhn.redhat.com/errata/RHBA-2016-0834.html Thank You Joe Kachuck Its not listed in the errata (RHBA-2016:0834-1) hence i was not certain how to point users to that for a fix. (In reply to Sumeet Keswani from comment #33) > Its not listed in the errata (RHBA-2016:0834-1) hence i was not certain how > to point users to that for a fix. This bug was fixed with RHBA-2016:0834-1 for Red Hat Enterprise Linux 6.8, under bug 1264189. That bug largely consists of private comments and is not very illuminating to external parties as a result. The upstream bug (https://sourceware.org/bugzilla/show_bug.cgi?id=19048) had a test.c and a check-free_list.sh script attached to it. Running the script against a running instance of the test exposes the bug on ppc64 and s390x (not sure why not on other architectures) even on the patched glibc. So this needs to be looked at again. Florian's doing that right now. Arjun, is this verified on both architectures, ppc64 and s390x ? (In reply to Georg Markgraf from comment #41) > Arjun, is this verified on both architectures, ppc64 and s390x ? Georg, yes the verification happened on all the rhel-7 supported architectures, incl ppc64 and s390x. ------- Comment From MSTRUBEL.com 2016-09-12 13:27 EDT------- I ran the arena tests (from glibc bugzilla) and did straces with and without TRIM option enabled using old & new glibc version. It seems the patches are effective. Thank you very much for taking care of this issue, I think, that this BZ can be closed now. best regards Matthias Strubel (In reply to IBM Bug Proxy from comment #43) > ------- Comment From MSTRUBEL.com 2016-09-12 13:27 EDT------- > I ran the arena tests (from glibc bugzilla) and did straces with and without > TRIM option enabled using old & new glibc version. It seems the patches are > effective. > > Thank you very much for taking care of this issue, Thank you for the additional testing. > I think, that this BZ can be closed now. This bug will be closed automatically once we ship the update as part of Red Hat Enterprise Linux 7.3. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2016-2573.html |