This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: malloc: performance improvements and bugfixes
- From: Jörn Engel <joern at purestorage dot com>
- To: Torvald Riegel <triegel at redhat dot com>
- Cc: "GNU C. Library" <libc-alpha at sourceware dot org>, Siddhesh Poyarekar <siddhesh dot poyarekar at gmail dot com>, Will Newton <will dot newton at linaro dot org>, Joern Engel <joern at purestorage dot org>
- Date: Tue, 26 Jan 2016 09:26:29 -0800
- Subject: Re: malloc: performance improvements and bugfixes
- Authentication-results: sourceware.org; auth=none
- References: <1453767872-19161-1-git-send-email-joern at purestorage dot com> <1453810961 dot 4592 dot 100 dot camel at localhost dot localdomain> <20160126171435 dot GG5745 at Sligo dot logfs dot org> <1453828825 dot 4592 dot 108 dot camel at localhost dot localdomain>
On Tue, Jan 26, 2016 at 06:20:25PM +0100, Torvald Riegel wrote:
>
> How do the allocation patterns look like? There can be big variations
> in allocation frequency and size, lifetime of allocated regions,
> relation between allocations and locality, etc. Some programs allocate
> most up-front, others have lots of alloc/dealloc during the lifetime of
> the program.
Lots of alloc/dealloc during the lifetime. To give you a rough scale,
malloc consumed around 1.7% cputime in the stable state. Now it is down
to about 0.7%.
JÃrn
--
When the people fear the government there is tyranny, when the government
fears the people there is liberty.
â Thomas Jefferson