CODEWITHSUNDEEP
iphoneobjective-cmultithreadingcocoaproperties
shosti
shosti

Reputation: 7422

Under what circumstances are atomic properties useful?

Objective-C properties default to atomic, which ensures that accessors are atomic but doesn't ensure overall thread-safety (as per this question). My question is, aren't atomic properties redundant in most concurrency scenarios? For example:

Scenario 1: mutable properties

@interface ScaryMutableObject : NSObject {}

@property (atomic, readwrite) NSMutableArray *stuff;

@end

void doStuffWith(ScaryMutableObject *obj) {
    [_someLock lock];
    [obj.stuff addObject:something]; //the atomic getter is completely redundant and could hurt performance
    [_someLock unlock];
}

//or, alternatively
void doStuffWith(ScaryMutableObject *obj) {
    NSMutableArray *cachedStuff = obj.stuff; //the atomic getter isn't redundant
    [_someLock lock];
    [cachedStuff addObject:something]; //but is this any more performant than using a nonatomic accessor within the lock?
    [_someLock unlock];   
}

Scenario 2: immutable properties

I was thinking that maybe atomic properties would be useful for avoiding locks when working with immutable objects, but since immutable objects can point to mutable objects in Objective-C, this isn't really much help:

@interface SlightlySaferObject : NSObject {}

@property (atomic, readwrite) NSArray *stuff;

@end

void doStuffWith(SlightlySaferObject *obj) {
    [[obj.stuff objectAtIndex:0] mutateLikeCrazy];//not at all thread-safe without a lock
}

The only scenarios I can think of where it's safe to use atomic accessors without a lock (and therefore worth using atomic properties at all) are:

  1. Working with properties that are primitives;
  2. Working with properties that are guaranteed to be immutable and not to point to mutable objects (such as an NSString or an NSArray of immutable objects).

Am I missing something? Are there any other good reasons to use atomic properties?

Upvotes: 6

Views: 2236

Answers (1)

bbum
bbum

Reputation: 162712

You aren't missing anything; atomic's usefulness is largely limited only to situations where you need to access or set a particular value from multiple threads where that value is also integral.

Beyond a single value, atomic cannot be used for thread safety purposes.

I wrote quite a bit about it in a weblog post a while ago.

This question is also a [very well posed] duplicate of What's the difference between the atomic and nonatomic attributes?

Upvotes: 6

Related Questions