FIFO serial queue using GCD

Question

I am trying to create a (network) synchronized array for the company I work for. While the networking part works fine, I have dwelled into an issue.

My wish was to create a new queue using dispatch_create_queue, to which I would add two blocks that are not to run on the main thread, but in a serial manner, meaning that first the first block has to run, then the second, and never in parallel.

I've read the apple documentation, but it is confusing to say the least.

When I create my queue using dispatch_queue_create and then add the blocks (after they have been defined) using dispatch_sync, I have found out that the block is still executing on the main thread.
When using dispatch_async, thats when the blocks are not executing on the main thread.
When I try to add both blocks using dispatch_sync They get blocked forever.
The only time that both blocks seem to run fine and off the main thread is when calling dispatch_async.

However the reason why I chose GCD and the sync method so that I was under the impression that I was creating a new queue (and thus a new thread) and that adding blocks to that queue would simply block one until the other had finished executing. Is this not the case, or does creating a queue does not guarantee that the code will not run on the main thread ?

Fernando Mazzon · Accepted Answer · 2013-01-02 20:39:39Z

67

This is a FIFO queue in GCD:

dispatch_queue_t serialQueue = dispatch_queue_create("com.blah.queue", DISPATCH_QUEUE_SERIAL);

...
dispatch_async(serialQueue, ^{
    //block1
});

dispatch_async(serialQueue, ^{
    //block2
});

answered Jan 2, 2013 at 20:39

Fernando Mazzon

3,5911 gold badge21 silver badges21 bronze badges

Sign up to request clarification or add additional context in comments.

12 Comments

Fernando Mazzon Over a year ago

The dispatch_async makes it so that the dispatch call itself doesn't block until the block is finished. If you use dispatch_sync, the task itself is executed in whatever thread the queue is in, but you block the current thread until the task is done. I don't think that's what you need.

jmstone617 Over a year ago

All dispatch queues are FIFO. Meaning that as long as you reuse the same queue, the order of block execution is determined and guaranteed not to lock and is thus thread-safe.

jmstone617 Over a year ago

@gnasher729 Even concurrent queues are technically FIFO. From Apple's documentation on concurrent queues: "Concurrent queues (also known as a type of global dispatch queue) execute one or more tasks concurrently, but tasks are still started in the order in which they were added to the queue."

PruitIgoe Over a year ago

@jmstone Wouldn't a concurrent queue be first in only? Since they are running in parallel you have no guarantee that the first job in will be the first job out? I've experienced this with making calls to Google's GeoCode API, where I've sent a series of queries that were stored in an array (addresses) and the returned JSON does not come back in the same order that I sent. I.E. Send Address1, Address2, Address3 in that order and the location data returned could be Location 2, Location 1, Location 3...

jmstone617 Over a year ago

@PruitIgoe FIFO does not mean FIFC (first in first to complete). Like I mentioned above, the FIFO order just guarantees that tasks are started in the order they were added to the queue. That doesn't mean they FINISH in the same order, as evidenced by the example you gave.

|

Collectives™ on Stack Overflow

FIFO serial queue using GCD

1 Answer 1

12 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

12 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related