On May 6, 2010, at 1:38 PM, McLaughlin, Michael P. wrote:
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
On Thu, May 6, 2010 at 1:38 PM, McLaughlin, Michael P. 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
wi
On 5/6/10 1:57 PM, "Jens Alfke" wrote:
>
>
> On May 6, 2010, at 10:34 AM, McLaughlin, Michael P. wrote:
>
>> Is there a recommended way of determining that the currentRunLoop in a
>> subordinate task (executable) is, in fact, running and ready to
>> receive a
>> distributed notification?
>
>
On May 6, 2010, at 10:34 AM, McLaughlin, Michael P. wrote:
Is there a recommended way of determining that the currentRunLoop in a
subordinate task (executable) is, in fact, running and ready to
receive a
distributed notification?
No. That's really not what distributed notifications are for
Is there a recommended way of determining that the currentRunLoop in a
subordinate task (executable) is, in fact, running and ready to receive a
distributed notification?
I have one subtask for each CPU, all launched during the init method of my
app. Each subtask responds with a "ready" message e
