获取进程线程信息
当发生 ANR 的时候，Android 系统会打印 CPU 相关的信息到日志中，使用的是ProcessCpuTracker
这样好像并没有权限可以拿到其他应用进程的 CPU 信息
当发现应用的某个进程 CPU 使用率比较高的时候，可以通过下面几个文件检查该进程下各个线程的 CPU 使用率，继而统计出该进程各个线程的时间占比。
/proc/[pid]/stat // 进程 CPU 使用情况
/proc/[pid]/task/[tid]/stat // 进程下面各个线程的 CPU 使用情况
/proc/[pid]/sched // 进程 CPU 调度相关
/proc/loadavg // 系统平均负载，uptime 命令对应文件
已将这部分逻辑加入网管监控中。代码cn.mwee.android.skynet.appruninfo.util.ProcessCpuTracker
如果需要获取线程信息打开开关 会获取以下信息](http://www.samirchen.com/linux-cpu-performance/)
CPU usage from 180344ms to 243ms ago (2019-02-21 20:54:48.521 to 2019-02-21 20:57:48.622): 0.5% 14771/com.mwee.android.pos.dinner:bizcenter(S): 0.3% user + 0.1% kernel / faults: 1367 minor thread stats: 0.1% 14979/thread_runtime_(R): 0.1% user + 0% kernel / faults: 162 minor 0% 15278/MYD_NetPool_114(S): 0% user + 0% kernel / faults: 193 minor 0% 14902/LogFileThread(S): 0% user + 0% kernel / faults: 296 minor 0% 14781/HeapTaskDaemon(S): 0% user + 0% kernel / faults: 168 minor 0% 14947/MYD_NetPool_114(S): 0% user + 0% kernel / faults: 64 minor 0% 8321/Smack Packet Re(S): 0% user + 0% kernel / faults: 291 minor 0% 14944/MYD_SLooper_114(S): 0% user + 0% kernel / faults: 57 minor 0% 8165/Smack Packet Re(S): 0% user + 0% kernel / faults: 294 minor 0% 14935/MWLog(S): 0% user + 0% kernel / faults: 13 minor 0% 14808/LogFileThread(S): 0% user + 0% kernel / faults: 69 minor 0% 14981/MYD_NetPool_114(S): 0% user + 0% kernel / faults: 13 minor 0% 14983/MYD_NetPool_114(S): 0% user + 0% kernel / faults: 13 minor 0% 15093/MYD_NetPool_114(S): 0% user + 0% kernel / faults: 3 minor 0% 15326/Smack Packet Re(S): 0% user + 0% kernel 0% 24139/Smack Listener (S): 0% user + 0% kernel 0% 24138/Smack Packet Re(S): 0% user + 0% kernel 0% 14771/inner:bizcenter(S): 0% user + 0% kernel / faults: 19 minor 0% 15061/Thread-403(S): 0% user + 0% kernel / faults: 4 minor 0% 14779/FinalizerDaemon(S): 0% user + 0% kernel 0% 14972/Binder_4(S): 0% user + 0% kernel / faults: 8 minor 0% 15009/MYD_SNetPool_11(S): 0% user + 0% kernel 0% 15156/MYD_xmpplink_al(S): 0% user + 0% kernel / faults: 6 minor 0% 14657/Binder_7(S): 0% user + 0% kernel 0% 14987/MYD_NetPool_114(S): 0% user + 0% kernel 0% 14938/WifiManager(S): 0% user + 0% kernel 0% 14789/Binder_2(S): 0% user + 0% kernel / faults: 2 minor 0% 14951/AlpAckLoop(S): 0% user + 0% kernel 0% 19106/Smack Listener (S): 0% user + 0% kernel / faults: 4 minor 0% 19105/Smack Packet Re(S): 0% user + 0% kernel / faults: 1 minor 0% 19104/Smack Packet Wr(S): 0% user + 0% kernel / faults: 6 minor 0% 14778/ReferenceQueueD(S): 0% user + 0% kernel 0% 5790/Binder_6(S): 0% user + 0% kernel 0% 26903/Binder_5(S): 0% user + 0% kernel 0% 14945/ClientHeartBeat(S): 0% user + 0% kernel 0% 14949/ALPServerLoop(S): 0% user + 0% kernel / faults: 4 minor 0% 14783/Binder_1(S): 0% user + 0% kernel 0% 14777/JDWP(S): 0% user + 0% kernel 0% 14960/Binder_3(S): 0% user + 0% kernel 0% 14939/Thread-379(S): 0% user + 0% kernel 0% 14941/Thread-381(S): 0% user + 0% kernel 0% 14940/Thread-380(S): 0% user + 0% kernel 0% 10446/OkHttp Connecti(S): 0% user + 0% kernel 0% 14885/Okio Watchdog(S): 0% user + 0% kernel 0% 14976/thread_runtime_(S): 0% user + 0% kernel 0% 14780/FinalizerWatchd(S): 0% user + 0% kernel 0% 14889/pool-1-thread-1(S): 0% user + 0% kernel 0% 15095/MYD_NetPool_114(S): 0% user + 0% kernel 0% 24137/Smack Packet Wr(S): 0% user + 0% kernel / faults: 1 minor 0% 9534/Smack Listener (S): 0% user + 0% kernel 0% 9511/Smack Packet Re(S): 0% user + 0% kernel 0% 9510/Smack Packet Wr(S): 0% user + 0% kernel / faults: 1 minor 0% 15163/MYD_NetPool_114(S): 0% user + 0% kernel 0% 14776/Signal Catcher(S): 0% user + 0% kernel 0% 15010/MYD_SNetPool_11(S): 0% user + 0% kernel 0% 14989/MYD_SNetPool_11(S): 0% user + 0% kernel 0% 14999/MYD_SNetPool_11(S): 0% user + 0% kernel 0% 14914/BuglyThread-3(S): 0% user + 0% kernel 0% 15094/MYD_NetPool_114(S): 0% user + 0% kernel 0% 14912/BuglyThread-1(S): 0% user + 0% kernel 0% 14818/BuglyThread-1(S): 0% user + 0% kernel 0% 14913/BuglyThread-2(S): 0% user + 0% kernel 0% 15325/Smack Packet Wr(S): 0% user + 0% kernel / faults: 1 minor 0% 15328/Smack Listener (S): 0% user + 0% kernel 0% 14888/OkHttp Connecti(S): 0% user + 0% kernel 0% 14858/MYD_NetPool_114(S): 0% user + 0% kernel 0% 14942/MYD_NetPool_114(S): 0% user + 0% kernel 0% 14859/MYD_NetPool_114(S): 0% user + 0% kernel 0% 14860/MYD_NetPool_114(S): 0% user + 0% kernel 0% 14819/BuglyThread-2(S): 0% user + 0% kernel 0% 14820/BuglyThread-3(S): 0% user + 0% kernel 0% 1495
上面是美易点业务中心的线程信息 。上面可以发现有几个重复的线程，bugly线程都重复了一次。这是由于不同classloader下 分别init了一次bugly。Android性能优化-线程性能优化
线程不是免费的：它们占用内存。每个线程最少消耗64k内存。如果设备上安装了许多应用，该值就会快速添加，特别是在调用栈显著增长的情况下
