This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [patch] malloc per-thread cache ready for review
- From: Carlos O'Donell <carlos at redhat dot com>
- To: Siddhesh Poyarekar <siddhesh at gotplt dot org>, Wilco Dijkstra <Wilco dot Dijkstra at arm dot com>, Markus Trippelsdorf <markus at trippelsdorf dot de>
- Cc: "dj at redhat dot com" <dj at redhat dot com>, nd <nd at arm dot com>, "libc-alpha at sourceware dot org" <libc-alpha at sourceware dot org>
- Date: Thu, 2 Feb 2017 08:14:48 -0500
- Subject: Re: [patch] malloc per-thread cache ready for review
- Authentication-results: sourceware.org; auth=none
- References: <AM5PR0802MB2610379A307A9AE5DD985482834C0@AM5PR0802MB2610.eurprd08.prod.outlook.com> <3e939569-6f3f-684e-e1b6-e96d1a8d9728@gotplt.org>
On 02/02/2017 07:01 AM, Siddhesh Poyarekar wrote:
> On Thursday 02 February 2017 05:23 PM, Wilco Dijkstra wrote:
>> I tried the new malloc (the patch as posted with several fixes from DJ's branch),
>> however I don't see any improvement on SPEC. That's odd since several subtests
>> spend ~10% of the time in malloc, and even with a single thread the locking is very
>> expensive, so bypassing it should give a good speedup. And yes having written
>
> That is very interesting, I'm going to look at this some more in the
> coming weeks. I had tested an earlier version (around December) but I
> didn't think the current one had any major improvements. Can you share
> what kind of machines you ran your tests one?
The next step would be to run with the high-speed API tracer turned on and
provide a trace of the application workload to see what's going on.
--
Cheers,
Carlos.