This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [updated patch] malloc per-thread cache ready for review
- From: DJ Delorie <dj at redhat dot com>
- To: Will Newton <will dot newton at gmail dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Fri, 17 Mar 2017 14:53:43 -0400
- Subject: Re: [updated patch] malloc per-thread cache ready for review
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx09.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx09.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=dj at redhat dot com
- Dkim-filter: OpenDKIM Filter v2.11.0 mx1.redhat.com B84D64DD4B
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com B84D64DD4B
Will Newton <will.newton@gmail.com> writes:
> It would be good to get wider testing of the performance on
> performance critical workloads that other people may have.
I've been collecting workloads for exactly that reason, using the tools
in the dj/malloc branch. With those, I can capture a site-specific
application's calls and repeat them elsewhere, in a generic environment.
My intention there is to create a corpus of such simulations, in order
to "represent" all these performance-critical apps during future malloc
work.
Now, if people would only send them to me, or at least tell me what
their performance critical workloads are ;-)