Re: jemalloc to replace default allocator
Re: jemalloc to replace default allocator
- Subject: Re: jemalloc to replace default allocator
- From: Jens Alfke <email@hidden>
- Date: Fri, 7 May 2010 15:12:14 -0700
On May 7, 2010, at 2:19 PM, Alastair Houghton wrote:
As I hinted, if it were *my* application, I'd be looking at why it's
calling free() so much. If that's happening, perhaps it's
allocating and releasing too much and maybe caching and re-using
objects might help (for instance).
I believe Joel said it's primarily JavaScript objects, and there's not
much the app can do about that. As a scripting language, JS creates
objects promiscuously, and the collector has to free them all.
(Collectors that do their own allocation can avoid most of the free
overhead, but not ones that are layered on malloc.)
—Jens _______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden