glibc 2.26 memory leak with MySQL?
Carlos O'Donell
carlos@redhat.com
Thu Aug 24 16:09:00 GMT 2017
On 08/24/2017 10:56 AM, DJ Delorie wrote:
> "Carlos O'Donell" <carlos@redhat.com> writes:
>> DJ,
>>
>> Do we have a rebased tracer against glibc 2.26?
>
> I've built a rawhide-based tracer (with F26 builds as well) and put the
> details and patches here:
>
> http://people.redhat.com/dj/glibc/
>
> Once a trace is captured and converted into a workload, it can be
> simulated on a range of platforms to see how they affect malloc
> performance, or inspected to try to analyze it.
Awesome. Thanks DJ!
Hopefully people can use this to test their workloads and get us
a trace to examine the performance.
--
Cheers,
Carlos.
More information about the Libc-help
mailing list