@synchronized有什么用

直接運行代碼

    //創(chuàng)建并發(fā)隊列
    dispatch_queue_t queue = dispatch_queue_create("", DISPATCH_QUEUE_CONCURRENT);
    for (NSInteger i = 0; i < 10; i++) {
        //異步 + 并發(fā)隊列 --> 系統(tǒng)會分配子線程
        dispatch_async(queue, ^{
            NSLog(@"+++%@",[NSThread currentThread]);
            NSLog(@"&&&%@ \t num:%@",[NSThread currentThread],@(i));
            NSLog(@"---%@",[NSThread currentThread]);
        });
    }

運行結果

2022-07-25 22:14:20.564617+0800 SyncDemo[1050:15060] +++<NSThread: 0x600002589580>{number = 6, name = (null)}
2022-07-25 22:14:20.564622+0800 SyncDemo[1050:15065] +++<NSThread: 0x6000025c15c0>{number = 4, name = (null)}
2022-07-25 22:14:20.564632+0800 SyncDemo[1050:15061] +++<NSThread: 0x600002594100>{number = 5, name = (null)}
2022-07-25 22:14:20.564617+0800 SyncDemo[1050:15062] +++<NSThread: 0x60000258ec80>{number = 7, name = (null)}
2022-07-25 22:14:20.564640+0800 SyncDemo[1050:15064] +++<NSThread: 0x60000258c140>{number = 3, name = (null)}
2022-07-25 22:14:20.564671+0800 SyncDemo[1050:15066] +++<NSThread: 0x60000258ed80>{number = 8, name = (null)}
2022-07-25 22:14:20.564673+0800 SyncDemo[1050:15065] &&&<NSThread: 0x6000025c15c0>{number = 4, name = (null)}    num:2
2022-07-25 22:14:20.564676+0800 SyncDemo[1050:15060] &&&<NSThread: 0x600002589580>{number = 6, name = (null)}    num:1
2022-07-25 22:14:20.564701+0800 SyncDemo[1050:15064] &&&<NSThread: 0x60000258c140>{number = 3, name = (null)}    num:4
2022-07-25 22:14:20.564761+0800 SyncDemo[1050:15065] ---<NSThread: 0x6000025c15c0>{number = 4, name = (null)}
2022-07-25 22:14:20.564737+0800 SyncDemo[1050:15066] &&&<NSThread: 0x60000258ed80>{number = 8, name = (null)}    num:5
2022-07-25 22:14:20.564769+0800 SyncDemo[1050:15062] &&&<NSThread: 0x60000258ec80>{number = 7, name = (null)}    num:0
2022-07-25 22:14:20.564775+0800 SyncDemo[1050:15068] +++<NSThread: 0x6000025c17c0>{number = 10, name = (null)}
2022-07-25 22:14:20.564778+0800 SyncDemo[1050:15061] &&&<NSThread: 0x600002594100>{number = 5, name = (null)}    num:3
2022-07-25 22:14:20.564777+0800 SyncDemo[1050:15067] +++<NSThread: 0x600002598300>{number = 9, name = (null)}
2022-07-25 22:14:20.564802+0800 SyncDemo[1050:15069] +++<NSThread: 0x6000025c5480>{number = 11, name = (null)}
2022-07-25 22:14:20.564918+0800 SyncDemo[1050:15060] ---<NSThread: 0x600002589580>{number = 6, name = (null)}
2022-07-25 22:14:20.564957+0800 SyncDemo[1050:15070] +++<NSThread: 0x600002587f40>{number = 12, name = (null)}
2022-07-25 22:14:20.565042+0800 SyncDemo[1050:15064] ---<NSThread: 0x60000258c140>{number = 3, name = (null)}
2022-07-25 22:14:20.565083+0800 SyncDemo[1050:15066] ---<NSThread: 0x60000258ed80>{number = 8, name = (null)}
2022-07-25 22:14:20.565246+0800 SyncDemo[1050:15067] &&&<NSThread: 0x600002598300>{number = 9, name = (null)}    num:6
2022-07-25 22:14:20.565283+0800 SyncDemo[1050:15068] &&&<NSThread: 0x6000025c17c0>{number = 10, name = (null)}   num:7
2022-07-25 22:14:20.565350+0800 SyncDemo[1050:15062] ---<NSThread: 0x60000258ec80>{number = 7, name = (null)}
2022-07-25 22:14:20.565426+0800 SyncDemo[1050:15070] &&&<NSThread: 0x600002587f40>{number = 12, name = (null)}   num:9
2022-07-25 22:14:20.565435+0800 SyncDemo[1050:15068] ---<NSThread: 0x6000025c17c0>{number = 10, name = (null)}
2022-07-25 22:14:20.565476+0800 SyncDemo[1050:15067] ---<NSThread: 0x600002598300>{number = 9, name = (null)}
2022-07-25 22:14:20.565549+0800 SyncDemo[1050:15061] ---<NSThread: 0x600002594100>{number = 5, name = (null)}
2022-07-25 22:14:20.565588+0800 SyncDemo[1050:15069] &&&<NSThread: 0x6000025c5480>{number = 11, name = (null)}   num:8
2022-07-25 22:14:20.584224+0800 SyncDemo[1050:15070] ---<NSThread: 0x600002587f40>{number = 12, name = (null)}
2022-07-25 22:14:20.584266+0800 SyncDemo[1050:15069] ---<NSThread: 0x6000025c5480>{number = 11, name = (null)}

分析:
1.首先要理解gcd造成的多線程糊饱,在當前的代碼中也就是dispatch_async{里面的三個NSLog在i為同一個值的時候+++&&&---的先后順序是固定的,但多個thread一起執(zhí)行,比如i == 1時thread_a+++&&&已經打印完了席镀,可能這時thread_b打印i == 3時的+++}

2.&&&和---出現(xiàn)的順序無法對應,可以看截圖更明顯
image.png

&&&7后面是&&&5疗锐,但是---7后面是---10愉豺。
這個時候使用@synchronized再跑一次看看會有什么變化。

dispatch_queue_t queue = dispatch_queue_create("", DISPATCH_QUEUE_CONCURRENT);
    for (NSInteger i = 0; i < 10; i++) {
        //異步 + 并發(fā)隊列 --> 系統(tǒng)會分配子線程
        dispatch_async(queue, ^{
            NSLog(@"+++%@",[NSThread currentThread]);
            //add @synchronized
            @synchronized (self) {
                NSLog(@"&&&%@ \t num:%@",[NSThread currentThread],@(i));
                NSLog(@"---%@",[NSThread currentThread]);
            }
        });
    }

打印結果如下

2022-07-25 22:29:25.413162+0800 SyncDemo[1215:25392] +++<NSThread: 0x600000304f00>{number = 6, name = (null)}
2022-07-25 22:29:25.413184+0800 SyncDemo[1215:25390] +++<NSThread: 0x600000300c80>{number = 4, name = (null)}
2022-07-25 22:29:25.413160+0800 SyncDemo[1215:25386] +++<NSThread: 0x600000350640>{number = 7, name = (null)}
2022-07-25 22:29:25.413193+0800 SyncDemo[1215:25388] +++<NSThread: 0x60000030cc80>{number = 8, name = (null)}
2022-07-25 22:29:25.413159+0800 SyncDemo[1215:25389] +++<NSThread: 0x600000350140>{number = 3, name = (null)}
2022-07-25 22:29:25.413191+0800 SyncDemo[1215:25387] +++<NSThread: 0x6000003094c0>{number = 5, name = (null)}
2022-07-25 22:29:25.413230+0800 SyncDemo[1215:25390] &&&<NSThread: 0x600000300c80>{number = 4, name = (null)}    num:4
2022-07-25 22:29:25.413245+0800 SyncDemo[1215:25395] +++<NSThread: 0x600000350800>{number = 9, name = (null)}
2022-07-25 22:29:25.413283+0800 SyncDemo[1215:25398] +++<NSThread: 0x600000307840>{number = 12, name = (null)}
2022-07-25 22:29:25.413264+0800 SyncDemo[1215:25396] +++<NSThread: 0x600000307580>{number = 10, name = (null)}
2022-07-25 22:29:25.413278+0800 SyncDemo[1215:25397] +++<NSThread: 0x600000351380>{number = 11, name = (null)}
2022-07-25 22:29:25.413301+0800 SyncDemo[1215:25390] ---<NSThread: 0x600000300c80>{number = 4, name = (null)}
2022-07-25 22:29:25.413525+0800 SyncDemo[1215:25392] &&&<NSThread: 0x600000304f00>{number = 6, name = (null)}    num:1
2022-07-25 22:29:25.413648+0800 SyncDemo[1215:25392] ---<NSThread: 0x600000304f00>{number = 6, name = (null)}
2022-07-25 22:29:25.413687+0800 SyncDemo[1215:25388] &&&<NSThread: 0x60000030cc80>{number = 8, name = (null)}    num:3
2022-07-25 22:29:25.413719+0800 SyncDemo[1215:25388] ---<NSThread: 0x60000030cc80>{number = 8, name = (null)}
2022-07-25 22:29:25.413780+0800 SyncDemo[1215:25395] &&&<NSThread: 0x600000350800>{number = 9, name = (null)}    num:6
2022-07-25 22:29:25.413851+0800 SyncDemo[1215:25395] ---<NSThread: 0x600000350800>{number = 9, name = (null)}
2022-07-25 22:29:25.413919+0800 SyncDemo[1215:25386] &&&<NSThread: 0x600000350640>{number = 7, name = (null)}    num:0
2022-07-25 22:29:25.413987+0800 SyncDemo[1215:25386] ---<NSThread: 0x600000350640>{number = 7, name = (null)}
2022-07-25 22:29:25.414039+0800 SyncDemo[1215:25396] &&&<NSThread: 0x600000307580>{number = 10, name = (null)}   num:7
2022-07-25 22:29:25.414087+0800 SyncDemo[1215:25396] ---<NSThread: 0x600000307580>{number = 10, name = (null)}
2022-07-25 22:29:25.414146+0800 SyncDemo[1215:25389] &&&<NSThread: 0x600000350140>{number = 3, name = (null)}    num:2
2022-07-25 22:29:25.416470+0800 SyncDemo[1215:25389] ---<NSThread: 0x600000350140>{number = 3, name = (null)}
2022-07-25 22:29:25.416521+0800 SyncDemo[1215:25397] &&&<NSThread: 0x600000351380>{number = 11, name = (null)}   num:8
2022-07-25 22:29:25.416553+0800 SyncDemo[1215:25397] ---<NSThread: 0x600000351380>{number = 11, name = (null)}
2022-07-25 22:29:25.416598+0800 SyncDemo[1215:25387] &&&<NSThread: 0x6000003094c0>{number = 5, name = (null)}    num:5
2022-07-25 22:29:25.416632+0800 SyncDemo[1215:25387] ---<NSThread: 0x6000003094c0>{number = 5, name = (null)}
2022-07-25 22:29:25.416679+0800 SyncDemo[1215:25398] &&&<NSThread: 0x600000307840>{number = 12, name = (null)}   num:9
2022-07-25 22:29:25.416717+0800 SyncDemo[1215:25398] ---<NSThread: 0x600000307840>{number = 12, name = (null)}

這次&&&后邊出現(xiàn)的第一個---所對應的thread一定能夠對應上务甥,結論就是:@synchronized{內部的代碼會保證在多線程的環(huán)境中thread_a執(zhí)行完所有邏輯才會thread_b進入執(zhí)行邏輯}

?著作權歸作者所有,轉載或內容合作請聯(lián)系作者
  • 序言:七十年代末牡辽,一起剝皮案震驚了整個濱河市,隨后出現(xiàn)的幾起案子敞临,更是在濱河造成了極大的恐慌态辛,老刑警劉巖,帶你破解...
    沈念sama閱讀 218,607評論 6 507
  • 序言:濱河連續(xù)發(fā)生了三起死亡事件挺尿,死亡現(xiàn)場離奇詭異奏黑,居然都是意外死亡,警方通過查閱死者的電腦和手機编矾,發(fā)現(xiàn)死者居然都...
    沈念sama閱讀 93,239評論 3 395
  • 文/潘曉璐 我一進店門熟史,熙熙樓的掌柜王于貴愁眉苦臉地迎上來,“玉大人窄俏,你說我怎么就攤上這事蹂匹。” “怎么了凹蜈?”我有些...
    開封第一講書人閱讀 164,960評論 0 355
  • 文/不壞的土叔 我叫張陵限寞,是天一觀的道長忍啸。 經常有香客問我,道長履植,這世上最難降的妖魔是什么计雌? 我笑而不...
    開封第一講書人閱讀 58,750評論 1 294
  • 正文 為了忘掉前任,我火速辦了婚禮玫霎,結果婚禮上凿滤,老公的妹妹穿的比我還像新娘。我一直安慰自己庶近,他們只是感情好翁脆,可當我...
    茶點故事閱讀 67,764評論 6 392
  • 文/花漫 我一把揭開白布。 她就那樣靜靜地躺著拦盹,像睡著了一般鹃祖。 火紅的嫁衣襯著肌膚如雪。 梳的紋絲不亂的頭發(fā)上普舆,一...
    開封第一講書人閱讀 51,604評論 1 305
  • 那天恬口,我揣著相機與錄音,去河邊找鬼沼侣。 笑死祖能,一個胖子當著我的面吹牛,可吹牛的內容都是我干的蛾洛。 我是一名探鬼主播养铸,決...
    沈念sama閱讀 40,347評論 3 418
  • 文/蒼蘭香墨 我猛地睜開眼,長吁一口氣:“原來是場噩夢啊……” “哼轧膘!你這毒婦竟也來了钞螟?” 一聲冷哼從身側響起,我...
    開封第一講書人閱讀 39,253評論 0 276
  • 序言:老撾萬榮一對情侶失蹤谎碍,失蹤者是張志新(化名)和其女友劉穎鳞滨,沒想到半個月后,有當?shù)厝嗽跇淞掷锇l(fā)現(xiàn)了一具尸體蟆淀,經...
    沈念sama閱讀 45,702評論 1 315
  • 正文 獨居荒郊野嶺守林人離奇死亡拯啦,尸身上長有42處帶血的膿包…… 初始之章·張勛 以下內容為張勛視角 年9月15日...
    茶點故事閱讀 37,893評論 3 336
  • 正文 我和宋清朗相戀三年,在試婚紗的時候發(fā)現(xiàn)自己被綠了熔任。 大學時的朋友給我發(fā)了我未婚夫和他白月光在一起吃飯的照片褒链。...
    茶點故事閱讀 40,015評論 1 348
  • 序言:一個原本活蹦亂跳的男人離奇死亡,死狀恐怖疑苔,靈堂內的尸體忽然破棺而出甫匹,到底是詐尸還是另有隱情,我是刑警寧澤,帶...
    沈念sama閱讀 35,734評論 5 346
  • 正文 年R本政府宣布兵迅,位于F島的核電站哀墓,受9級特大地震影響,放射性物質發(fā)生泄漏喷兼。R本人自食惡果不足惜,卻給世界環(huán)境...
    茶點故事閱讀 41,352評論 3 330
  • 文/蒙蒙 一后雷、第九天 我趴在偏房一處隱蔽的房頂上張望季惯。 院中可真熱鬧,春花似錦臀突、人聲如沸勉抓。這莊子的主人今日做“春日...
    開封第一講書人閱讀 31,934評論 0 22
  • 文/蒼蘭香墨 我抬頭看了看天上的太陽藕筋。三九已至,卻和暖如春梳码,著一層夾襖步出監(jiān)牢的瞬間隐圾,已是汗流浹背。 一陣腳步聲響...
    開封第一講書人閱讀 33,052評論 1 270
  • 我被黑心中介騙來泰國打工掰茶, 沒想到剛下飛機就差點兒被人妖公主榨干…… 1. 我叫王不留暇藏,地道東北人。 一個月前我還...
    沈念sama閱讀 48,216評論 3 371
  • 正文 我出身青樓濒蒋,卻偏偏與公主長得像盐碱,于是被迫代替她去往敵國和親。 傳聞我的和親對象是個殘疾皇子沪伙,可洞房花燭夜當晚...
    茶點故事閱讀 44,969評論 2 355

推薦閱讀更多精彩內容