Re: Timing distributed notifications
Re: Timing distributed notifications
- Subject: Re: Timing distributed notifications
- From: Kyle Sluder <email@hidden>
- Date: Thu, 6 May 2010 13:44:44 -0700
On Thu, May 6, 2010 at 1:38 PM, McLaughlin, Michael P. <email@hidden> wrote:
> I tried for a long time to get threads to work but they did not, even to the
> extent, sometimes, of seeing reverse scaling (longer runtimes with more
> threads).
How about Grand Central Dispatch? A lot of the problems people have
with threading stem from using too many threads. GCD should be smarter
about thread pooling.
> The reason, in my case, is almost certainly malloc contention (since threads
> share memory space). Each of my subtasks calls malloc more than a million
> times even for an average run. These are mostly dynamic allocations of
> vectors and matrices as well as smaller numbers of lists, sets and maps.
Perhaps you should switch to a custom allocator outright. It might
speed up your program overall.
--Kyle Sluder
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden