Splitting for length, part 1... I will also attach a sample crash report. So, let me start there. All three logs have threads blocked in dispatch_sync, with the worst case having 35 threads blocked in this code chunk waiting for another thread to clear the block: 6 libdispatch.dylib 0x7ff80f50468e _dispatch_sync_f_slow + 175 7 com.proofpoint.itm.prevention 0x10a102a81 8 com.proofpoint.itm.prevention 0x10a0ff5cb 9 com.proofpoint.itm.prevention 0x10a0ff482 10 com.proofpoint.itm.prevention 0x10a0c5716 11 libdispatch.dylib 0x7ff80f4f76b9 _dispatch_call_block_and_release + 12 The other two logs are that extreme, but both of them also show blocks in dispatch_sync and one of them also shows the same contentions (though not as extreme). I have some general comments below, but the critical next step here is to fully symbolicate these logs and figure out what your client is actually doing. You're clearly bottlenecking on something and figuring out what that is is obviously an important first step. I obviously don't kno
Topic:
App & System Services
SubTopic:
Core OS
Tags: