Re: autorelease: how does this work!? (if at all)
Re: autorelease: how does this work!? (if at all)
- Subject: Re: autorelease: how does this work!? (if at all)
- From: Tony Romano <email@hidden>
- Date: Fri, 18 Jun 2010 12:39:22 -0700
I did notice the inner block was running on a second q, that's what my comment is about. I guess the first block what's really in questioned, how big is the images?? If it will block, then put it in the same block as the write. I'm assuming you want he image transformed prior to the write.
-Tony
On Jun 18, 2010, at 12:20 PM, Jonny Taylor wrote:
>> First, the objects are retained by dispatch_async as others have mentioned. Second, I'm not sure why you used 2 queues for the tasks in your code, seems overly complex. Async queues are serialized, which means that you can continue to add to the queue and the jobs will be done in order which they were added. The next job will not start until the previous one in the queue is completed.
> Possibly overly complex, but notice that the nested block is running on *a different queue* to the block that spawns it. My intention is that the "write" queue (running the nested block) can have a write outstanding at all times, maximizing the rate at which data can be written to disk. To be fair the outer block does not strictly require a dedicated queue - it could probably run equally well on the global concurrent queue - but I don't think that's what you're commenting on is it?
-Tony
_______________________________________________
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