Re: How turn-off C-run time library memory diagnostics?
Re: How turn-off C-run time library memory diagnostics?
- Subject: Re: How turn-off C-run time library memory diagnostics?
- From: Gen Kiyooka <email@hidden>
- Date: Fri, 5 Aug 2005 12:16:24 -0700
On Aug 5, 2005, at 12:13 PM, Scott Ribe wrote:
System-provided malloc/free can't be expected to be high-performers,
because they don't know anything about
your application's algorithm or memory usage patterns.
Sometime around Jaguar/Panther Apple claimed to have implemented
high-performance multi-threaded malloc/free in the standard
libraries. I
haven't had occasion to test those claims.
Granted, a custom allocator can often do better for specific
application-dependent patterns of use, but much of the "system-
provided
can't be expected to..." arguments I've seen over the years were
just weak
excuses for simple-minded implementations. For instance: CW did
pretty well,
SmartHeap was fantastic, the one in Symantec Think C++ 6 was a
stinking pile
of garbage.
Yep, SmartHeap was great. I used to demo RoboHelp at the same
tradeshows
as those guys in '92/93 or so. I built my own allocators based on
some of their
ideas. Subsegment allocation is the way to go, especially for C++,
given the
copious amounts of allocations that the stl issues.
Gen
--
Scott Ribe
email@hidden
http://www.killerbytes.com/
(303) 665-7007 voice
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden