操作系统性能调试IO性能分析（国外英文资料）.doc

操作系统性能调试IO性能分析（国外英文资料） 1: measure the level of leisure of I/O 2: I/O resources are a symptom of a bottleneck in system performance 3: which activities are the biggest contributors to the I/O resources? 4: use iostat to analyze the utilization of I/O 5: analyze disk activity using the SAR command 6: analyze the activity of the buffer using the SAR command 7: use the SAR command to analyze the activity in the swap area 8: using the GlancePlus analysis system I/O activity 9: performance debugging for I/O requirements intensive systems Measure the level of leisure of I/O Here are some indicators of how busy I/O is: Disk utilization (disk utilization) Disk queue length (disk queue length) Read/write rates per logical volume (read/write rates per logical volume) Raw I/O (raw I/O) : primarily for database applications Swap queue length (swap queue length) Buffer cache hit ratio Network file system and undisk workstation rate (NFS and diskless rates (server)) I/O resources become a symptom of system performance bottlenecks When I/O becomes a bottleneck, the following typical symptoms occur: High disk utilization Too long disk queue length The percentage of time waiting for disk I/O is too high (large percentage of time waiting for disk I/O) High physical I/O rate: large physical I/O rate Low buffer cache hit ratio (not sufficient in itself) Too long running the process queue, but the CPU is idle (the large run queue with idle CPU) Which activities are the biggest contributors to the I/O resources? Here are some activities that take up a lot of the I/O resources: Paging: paging not only causes memory problems, but also causes disk problems; Open, creat, and stat system calls: system calls cause a lot of disk I/O; Multiuser I/O and random I/O Relational database The core dumps Use iostat to analyze the utilization of I/O Iostat - report I/O statistics Iostat iteratively reports I/O statistics for each active disk on the system. If two or more disks are presented, data is pres