iOS 多线程之 GCD

介绍

Dispatch, also known as Grand Central Dispatch (GCD), contains language features, runtime libraries, and system enhancements that provide systemic, comprehensive improvements to the support for concurrent code execution on multicore hardware in macOS, iOS, watchOS, and tvOS.

优势

  • GCD 会自动管理线程的生命周期
  • RD 只需要将指定任务特定方式提交到相应队列

概念

指定任务

将要执行的操作
typedef void (^dispatch_block_t)(void);

特定方式

同步执行(sync)

  1. 等待同步任务结束后再继续执行当前任务
  2. 两个任务在同一线程执行,具备开启线程能力
    同步执行

异步执行(async)

  1. 提交异步任务后立即继续执行当前任务
  2. 两个任务可以在不同线程中执行,具备开启线程能力


    异步执行

异步执行虽然具有开启新线程的能力,但是并不一定开启新线程

相应队列

队列概念

队列是一种特殊的线性表,采用 FIFO(先进先出)的原则


队列

串行队列

  1. 所有任务按顺序依次执行,结束顺序固定
  2. 队列头部的任务等待上一个任务执行完毕后才出队列


    串行队列

并发队列

  1. 所有任务可以同时执行,结束顺序固定
  2. 只要有可用线程,则队列头部任务将持续出队列


    并发队列

队列和线程没有必然联系,队列只是一系列任务的容器,而线程才是执行任务的载体。
所以,不要认为串行队列中的所有任务都在同一个线程中。

实战

实战 1

在主线程中执行如下代码

    self.serial_queue = dispatch_queue_create("def.test.serial", DISPATCH_QUEUE_SERIAL);
    
    NSLog(@"liyc: a thread %@", [NSThread currentThread]);
    for (NSUInteger i = 0; i < 5; i++) {
        dispatch_async(self.serial_queue, ^{
            NSLog(@"liyc: %@ thread %@", @(i), [NSThread currentThread]);
        });
    }
    
    NSLog(@"liyc: b thread %@", [NSThread currentThread]);
    for (NSUInteger i = 5; i < 10; i++) {
        dispatch_sync(self.serial_queue, ^{
            NSLog(@"liyc: %@ thread %@", @(i), [NSThread currentThread]);
        });
    }

分析如下:
在主线程中提交五个异步任务,由于是异步,所以继续在主线程执行当前任务。第二个for循环将要添加五个同步任务,此时需要等待新添加的同步任务执行完毕,而在这之前队列中已经存在五个任务,所以要先依次执行完毕后才能继续执行。那么得到如下结果:

2019-08-22 16:04:19.610366+0800 ThreadDemo[81233:4928855] liyc: a thread <NSThread: 0x600001d213c0>{number = 1, name = main}
2019-08-22 16:04:19.610560+0800 ThreadDemo[81233:4928855] liyc: b thread <NSThread: 0x600001d213c0>{number = 1, name = main}
2019-08-22 16:04:19.610597+0800 ThreadDemo[81233:4928907] liyc: 0 thread <NSThread: 0x600001d54700>{number = 3, name = (null)}
2019-08-22 16:04:19.610699+0800 ThreadDemo[81233:4928907] liyc: 1 thread <NSThread: 0x600001d54700>{number = 3, name = (null)}
2019-08-22 16:04:19.610802+0800 ThreadDemo[81233:4928907] liyc: 2 thread <NSThread: 0x600001d54700>{number = 3, name = (null)}
2019-08-22 16:04:19.610895+0800 ThreadDemo[81233:4928907] liyc: 3 thread <NSThread: 0x600001d54700>{number = 3, name = (null)}
2019-08-22 16:04:19.610999+0800 ThreadDemo[81233:4928907] liyc: 4 thread <NSThread: 0x600001d54700>{number = 3, name = (null)}
2019-08-22 16:04:19.611128+0800 ThreadDemo[81233:4928855] liyc: 5 thread <NSThread: 0x600001d213c0>{number = 1, name = main}
2019-08-22 16:04:19.611225+0800 ThreadDemo[81233:4928855] liyc: 6 thread <NSThread: 0x600001d213c0>{number = 1, name = main}
2019-08-22 16:04:19.611310+0800 ThreadDemo[81233:4928855] liyc: 7 thread <NSThread: 0x600001d213c0>{number = 1, name = main}
2019-08-22 16:04:19.759665+0800 ThreadDemo[81233:4928855] liyc: 8 thread <NSThread: 0x600001d213c0>{number = 1, name = main}
2019-08-22 16:04:19.759772+0800 ThreadDemo[81233:4928855] liyc: 9 thread <NSThread: 0x600001d213c0>{number = 1, name = main}

问题:b一定紧随a之后输出吗?
回答:不是的。大家看到1~4在子线程中,所以理论上b有可能在a之后5之前的任意位置。
大家感兴趣的话可以自己测试一下,在两个for循环之间加个耗时操作。

实战 2

在主线程中执行如下代码

    self.serial_queue = dispatch_get_main_queue();
    
    NSLog(@"liyc: a thread %@", [NSThread currentThread]);
    for (NSUInteger i = 0; i < 5; i++) {
        dispatch_async(self.serial_queue, ^{
            NSLog(@"liyc: %@ thread %@", @(i), [NSThread currentThread]);
        });
    }
    
    NSLog(@"liyc: b thread %@", [NSThread currentThread]);
    for (NSUInteger i = 5; i < 10; i++) {
        dispatch_sync(self.serial_queue, ^{
            NSLog(@"liyc: %@ thread %@", @(i), [NSThread currentThread]);
        });
    }

分析如下:
在主线程中提交五个异步任务,由于是异步,所以继续在主线程执行当前任务。第二个for循环将要添加五个同步任务,此时需要等待新添加的同步任务执行完毕,而在这之前队列中已经存在五个任务,所以要先依次执行完毕后才能继续执行。
以上与刚才一样,但是,问题来了:当前任务是在主队列里出来的,并没有执行完毕,此时又想将主队列里的头部任务取出,而主队列是串行队列,取出队列头部又需要已经出队列的任务执行完毕。造成相互等待,程序无法继续执行。那么得到如下结果:

2019-08-22 16:12:23.248246+0800 ThreadDemo[81337:4935835] liyc: a thread <NSThread: 0x600003ac1dc0>{number = 1, name = main}
2019-08-22 16:12:23.248468+0800 ThreadDemo[81337:4935835] liyc: b thread <NSThread: 0x600003ac1dc0>{number = 1, name = main}

实战 3

在主线程中执行如下代码

    self.concurrent_queue = dispatch_queue_create("def.test.concurrent", DISPATCH_QUEUE_CONCURRENT);

    NSLog(@"liyc: c thread %@", [NSThread currentThread]);
    for (NSUInteger i = 10; i < 15; i++) {
        dispatch_sync(self.concurrent_queue, ^{
            NSLog(@"liyc: %@ thread %@", @(i), [NSThread currentThread]);
        });
    }
    
    NSLog(@"liyc: d thread %@", [NSThread currentThread]);
    for (NSUInteger i = 15; i < 20; i++) {
        dispatch_async(self.concurrent_queue, ^{
            NSLog(@"liyc: %@ thread %@", @(i), [NSThread currentThread]);
        });
    }    

分析如下:
将要在主线程中提交五个同步任务,由于是同步,所以五个任务依次被加入队列,并且执行。之后异步加入并发队列,所以乱序的情况下在不同线程里被执行。那么得到如下结果:

2019-08-22 16:27:17.104961+0800 ThreadDemo[81497:4949380] liyc: c thread <NSThread: 0x600001b692c0>{number = 1, name = main}
2019-08-22 16:27:17.105134+0800 ThreadDemo[81497:4949380] liyc: 10 thread <NSThread: 0x600001b692c0>{number = 1, name = main}
2019-08-22 16:27:17.105239+0800 ThreadDemo[81497:4949380] liyc: 11 thread <NSThread: 0x600001b692c0>{number = 1, name = main}
2019-08-22 16:27:17.105332+0800 ThreadDemo[81497:4949380] liyc: 12 thread <NSThread: 0x600001b692c0>{number = 1, name = main}
2019-08-22 16:27:17.105434+0800 ThreadDemo[81497:4949380] liyc: 13 thread <NSThread: 0x600001b692c0>{number = 1, name = main}
2019-08-22 16:27:17.105523+0800 ThreadDemo[81497:4949380] liyc: 14 thread <NSThread: 0x600001b692c0>{number = 1, name = main}
2019-08-22 16:27:17.105625+0800 ThreadDemo[81497:4949380] liyc: d thread <NSThread: 0x600001b692c0>{number = 1, name = main}
2019-08-22 16:27:17.105767+0800 ThreadDemo[81497:4949454] liyc: 15 thread <NSThread: 0x600001b0cdc0>{number = 3, name = (null)}
2019-08-22 16:27:17.105778+0800 ThreadDemo[81497:4949452] liyc: 16 thread <NSThread: 0x600001b02d00>{number = 4, name = (null)}
2019-08-22 16:27:17.105815+0800 ThreadDemo[81497:4949453] liyc: 17 thread <NSThread: 0x600001b60100>{number = 5, name = (null)}
2019-08-22 16:27:17.105821+0800 ThreadDemo[81497:4949451] liyc: 19 thread <NSThread: 0x600001b287c0>{number = 6, name = (null)}
2019-08-22 16:27:17.105834+0800 ThreadDemo[81497:4949464] liyc: 18 thread <NSThread: 0x600001b02ac0>{number = 7, name = (null)}

问题:d一定在14之后输出吗?
回答:是的。因为上边是同步任务。

实战 4

在主线程中执行如下代码

    self.concurrent_queue = dispatch_queue_create("def.test.concurrent", DISPATCH_QUEUE_CONCURRENT);

    NSLog(@"liyc: c thread %@", [NSThread currentThread]);
    for (NSUInteger i = 10; i < 15; i++) {
        NSLog(@"liyc: i-%@ thread %@", @(i), [NSThread currentThread]);
        dispatch_sync(self.concurrent_queue, ^{
            NSLog(@"liyc: %@ thread %@", @(i), [NSThread currentThread]);
        });
    }
    
    NSLog(@"liyc: d thread %@", [NSThread currentThread]);
    for (NSUInteger i = 15; i < 20; i++) {
        NSLog(@"liyc: i-%@ thread %@", @(i), [NSThread currentThread]);
        dispatch_async(self.concurrent_queue, ^{
            NSLog(@"liyc: %@ thread %@", @(i), [NSThread currentThread]);
        });
    }    

分析如下:
这里和实战 3的区别是在for循环里添加了i-输出。主要是理解for循环是连续执行,还是等待加入的任务执行完毕后再继续执行循环。那么得到如下结果:

2019-08-22 16:43:37.960402+0800 ThreadDemo[81711:4964687] liyc: c thread <NSThread: 0x6000000c13c0>{number = 1, name = main}
2019-08-22 16:43:37.960534+0800 ThreadDemo[81711:4964687] liyc: i-10 thread <NSThread: 0x6000000c13c0>{number = 1, name = main}
2019-08-22 16:43:37.960652+0800 ThreadDemo[81711:4964687] liyc: 10 thread <NSThread: 0x6000000c13c0>{number = 1, name = main}
2019-08-22 16:43:37.960768+0800 ThreadDemo[81711:4964687] liyc: i-11 thread <NSThread: 0x6000000c13c0>{number = 1, name = main}
2019-08-22 16:43:37.960911+0800 ThreadDemo[81711:4964687] liyc: 11 thread <NSThread: 0x6000000c13c0>{number = 1, name = main}
2019-08-22 16:43:37.961027+0800 ThreadDemo[81711:4964687] liyc: i-12 thread <NSThread: 0x6000000c13c0>{number = 1, name = main}
2019-08-22 16:43:37.961127+0800 ThreadDemo[81711:4964687] liyc: 12 thread <NSThread: 0x6000000c13c0>{number = 1, name = main}
2019-08-22 16:43:37.961254+0800 ThreadDemo[81711:4964687] liyc: i-13 thread <NSThread: 0x6000000c13c0>{number = 1, name = main}
2019-08-22 16:43:37.961358+0800 ThreadDemo[81711:4964687] liyc: 13 thread <NSThread: 0x6000000c13c0>{number = 1, name = main}
2019-08-22 16:43:37.961474+0800 ThreadDemo[81711:4964687] liyc: i-14 thread <NSThread: 0x6000000c13c0>{number = 1, name = main}
2019-08-22 16:43:37.961581+0800 ThreadDemo[81711:4964687] liyc: 14 thread <NSThread: 0x6000000c13c0>{number = 1, name = main}
2019-08-22 16:43:37.961690+0800 ThreadDemo[81711:4964687] liyc: d thread <NSThread: 0x6000000c13c0>{number = 1, name = main}
2019-08-22 16:43:37.966989+0800 ThreadDemo[81711:4964687] liyc: i-15 thread <NSThread: 0x6000000c13c0>{number = 1, name = main}
2019-08-22 16:43:37.967175+0800 ThreadDemo[81711:4964687] liyc: i-16 thread <NSThread: 0x6000000c13c0>{number = 1, name = main}
2019-08-22 16:43:37.967201+0800 ThreadDemo[81711:4964889] liyc: 15 thread <NSThread: 0x6000000b03c0>{number = 3, name = (null)}
2019-08-22 16:43:37.967363+0800 ThreadDemo[81711:4964687] liyc: i-17 thread <NSThread: 0x6000000c13c0>{number = 1, name = main}
2019-08-22 16:43:37.967380+0800 ThreadDemo[81711:4964889] liyc: 16 thread <NSThread: 0x6000000b03c0>{number = 3, name = (null)}
2019-08-22 16:43:37.967492+0800 ThreadDemo[81711:4964687] liyc: i-18 thread <NSThread: 0x6000000c13c0>{number = 1, name = main}
2019-08-22 16:43:37.967496+0800 ThreadDemo[81711:4964889] liyc: 17 thread <NSThread: 0x6000000b03c0>{number = 3, name = (null)}
2019-08-22 16:43:37.967625+0800 ThreadDemo[81711:4964889] liyc: 18 thread <NSThread: 0x6000000b03c0>{number = 3, name = (null)}
2019-08-22 16:43:37.967626+0800 ThreadDemo[81711:4964687] liyc: i-19 thread <NSThread: 0x6000000c13c0>{number = 1, name = main}
2019-08-22 16:43:37.967802+0800 ThreadDemo[81711:4964891] liyc: 19 thread <NSThread: 0x6000000bc000>{number = 4, name = (null)}

如果以上这些内容全部理解了,那么关于GCD的使用问题应该就不大了。实战代码看这里

其他

  • dispatch_barrier_async
  • dispatch_after
  • dispatch_once
  • dispatch_apply
  • dispatch_group
    • dispatch_group_notify
    • dispatch_group_wait
    • dispatch_group_enter/dispatch_group_leave
  • dispatch_semaphore

最后

线程切换存在成本,需要酌情使用。但是如果只是把任务抛到子线程去处理,那么几乎没有开销。所以大可以放心使用,比如,监控、埋点相关操作,都可以放到子线程中执行。

引用

最后编辑于
©著作权归作者所有,转载或内容合作请联系作者
  • 序言:七十年代末,一起剥皮案震惊了整个滨河市,随后出现的几起案子,更是在滨河造成了极大的恐慌,老刑警刘岩,带你破解...
    沈念sama阅读 158,560评论 4 361
  • 序言:滨河连续发生了三起死亡事件,死亡现场离奇诡异,居然都是意外死亡,警方通过查阅死者的电脑和手机,发现死者居然都...
    沈念sama阅读 67,104评论 1 291
  • 文/潘晓璐 我一进店门,熙熙楼的掌柜王于贵愁眉苦脸地迎上来,“玉大人,你说我怎么就摊上这事。” “怎么了?”我有些...
    开封第一讲书人阅读 108,297评论 0 243
  • 文/不坏的土叔 我叫张陵,是天一观的道长。 经常有香客问我,道长,这世上最难降的妖魔是什么? 我笑而不...
    开封第一讲书人阅读 43,869评论 0 204
  • 正文 为了忘掉前任,我火速办了婚礼,结果婚礼上,老公的妹妹穿的比我还像新娘。我一直安慰自己,他们只是感情好,可当我...
    茶点故事阅读 52,275评论 3 287
  • 文/花漫 我一把揭开白布。 她就那样静静地躺着,像睡着了一般。 火红的嫁衣衬着肌肤如雪。 梳的纹丝不乱的头发上,一...
    开封第一讲书人阅读 40,563评论 1 216
  • 那天,我揣着相机与录音,去河边找鬼。 笑死,一个胖子当着我的面吹牛,可吹牛的内容都是我干的。 我是一名探鬼主播,决...
    沈念sama阅读 31,833评论 2 312
  • 文/苍兰香墨 我猛地睁开眼,长吁一口气:“原来是场噩梦啊……” “哼!你这毒妇竟也来了?” 一声冷哼从身侧响起,我...
    开封第一讲书人阅读 30,543评论 0 197
  • 序言:老挝万荣一对情侣失踪,失踪者是张志新(化名)和其女友刘颖,没想到半个月后,有当地人在树林里发现了一具尸体,经...
    沈念sama阅读 34,245评论 1 241
  • 正文 独居荒郊野岭守林人离奇死亡,尸身上长有42处带血的脓包…… 初始之章·张勋 以下内容为张勋视角 年9月15日...
    茶点故事阅读 30,512评论 2 244
  • 正文 我和宋清朗相恋三年,在试婚纱的时候发现自己被绿了。 大学时的朋友给我发了我未婚夫和他白月光在一起吃饭的照片。...
    茶点故事阅读 32,011评论 1 258
  • 序言:一个原本活蹦乱跳的男人离奇死亡,死状恐怖,灵堂内的尸体忽然破棺而出,到底是诈尸还是另有隐情,我是刑警宁泽,带...
    沈念sama阅读 28,359评论 2 253
  • 正文 年R本政府宣布,位于F岛的核电站,受9级特大地震影响,放射性物质发生泄漏。R本人自食恶果不足惜,却给世界环境...
    茶点故事阅读 33,006评论 3 235
  • 文/蒙蒙 一、第九天 我趴在偏房一处隐蔽的房顶上张望。 院中可真热闹,春花似锦、人声如沸。这庄子的主人今日做“春日...
    开封第一讲书人阅读 26,062评论 0 8
  • 文/苍兰香墨 我抬头看了看天上的太阳。三九已至,却和暖如春,着一层夹袄步出监牢的瞬间,已是汗流浃背。 一阵脚步声响...
    开封第一讲书人阅读 26,825评论 0 194
  • 我被黑心中介骗来泰国打工, 没想到刚下飞机就差点儿被人妖公主榨干…… 1. 我叫王不留,地道东北人。 一个月前我还...
    沈念sama阅读 35,590评论 2 273
  • 正文 我出身青楼,却偏偏与公主长得像,于是被迫代替她去往敌国和亲。 传闻我的和亲对象是个残疾皇子,可洞房花烛夜当晚...
    茶点故事阅读 35,501评论 2 268

推荐阅读更多精彩内容