Skip to main content

(iOS) dispatch_async() vs. NSOperationQueue

source: http://stackoverflow.com/questions/11676629/ios-dispatch-async-vs-nsoperationqueue
NSOperation* classes are the higher level api. They hide GCD's lower level api from you so that you can concentrate on getting the task done.
The rule of thumb is: Use the api of the highest level first and then degrade based on what you need to accomplish.
The advantage of this approach is that your code stays most agnostic to the specific implementation the vendor provides. In this example, using NSOperation, you'll be using Apple's implementation of execution queueing (using GCD). Should Apple ever decide to change the details of implementation behind the scenes they can do so without breaking your application's code.
One such example would be Apple deprecating GCD and using a completely different library (which is unlikely because Apple created GCD and everybody seems to love it).
Regarding the matter i recommend consulting the following resources:
Now, regarding your specific questions:
What are the differences between dispatch_*() and NSOperationQueue, [...]
See above.
[...] and is there any reason (technical, performance, stylistic, or otherwise) that I should use one over the other?
If the NSOperation stuff gets your job done, use it.
Is NSOperationQueue just an Objective-C wrapper around dispatch_async, or is there more to it than that?
Yes, it basically is. Plus features like operation dependencies, easy start/stop.

Amendment

To say, use the highest level api first might sound intriguing. Of course, if you need a quick way to run code on a specific thread, you don't want to write a whole lot of boilerplate code which makes the use of lower level C functions perfectly valid:
dispatch_async(dispatch_get_main_queue(), ^{
  do_something();
});
But consider this:
[[NSOperationQueue mainQueue] addOperationWithBlock:^{
  do_something();
}];
I'd recommend the latter because most of what you'll write is Objective-C anyway so why not embrace its expressiveness?

Comments

Popular posts from this blog

Stretch a row if data overflows in jasper reports

It is very common that some columns of the report need to stretch to show all the content in that column. But  if you just specify the property " stretch with overflow' to that column(we called text field in jasper report world) , it will just stretch that column and won't change other columns, so the row could be ridiculous. Haven't find the solution from internet yet. So I just review the properties in iReport one by one and find two useful properties(the bold highlighted in example below) which resolve the problems.   example:
<band height="20" splitType="Stretch"> <textField isStretchWithOverflow="true" pattern="" isBlankWhenNull="true"> <reportElement stretchType="RelativeToTallestObject" mode="Opaque" x="192" y="0" width="183" height="20"/> <box leftPadding="2"> <pen lineWidth="0.25"/> …

JasperReports - Configuration Reference

Live - solving the jasper report out of memory and high cpu usage problems

I still can not find the solution. So I summary all the things and tell my boss about it. If any one knows the solution, please let me know.


Symptom: 1.The JVM became Out of memory when creating big consumption report 2.Those JRTemplateElement-instances is still there occupied even if I logged out the system
Reason:         1. There is a large number of JRTemplateElement-instances cached in the memory 2.The clearobjects() method in ReportThread class has not been triggered when logging out
Action I tried:      About the Virtualizer: 1.Replacing the JRSwapFileVirtualizer with JRFileVirtualizer 2.Not use any FileVirtualizer for cache the report in the hard disk Result: The japserreport still creating the a large number of JRTemplateElement-instances in the memory     About the work around below,      I tried: item 3(in below work around list) – result: it helps to reduce  the size of the JRTemplateElement Object                Item 4,5 – result : it helps a lot to reduce the number of  JRTemplateE…