SYS 140: I O Lab - WanderlustPenguin/Charles-Tech-Journal GitHub Wiki

Performance Monitor Reports can be very useful for identifying possible I/O issues affecting a computer. They consolidate extensive information on the chosen areas into an easier to read report, and explain how the system itself is operating. It gives information on several areas where performance issues might occur: from the CPU, the network, the disk, and memory. It also gives subcategories for all of these. The report also gives statistics on how it went about gathering this information, which can be helpful if you need to understand how it found the things it did, or want more information on how the process went and any issues that occured.

One circumstance this style of report might be useful in is where there are issues occurring in one specific area of the computer, but you don’t know where. By using this report you can pin down where the issues are occurring with much more ease than trying to manually find it; for example finding out if an issue with recovering information stems from memory issues or the CPU itself running into problems. This report is also helpful if someone wants to get a proactive report to identify any problems with the computer. This report can help give an idea of how the computer is doing in several areas, which can help with identifying issues it’s having before they become larger problems that hinder the computer’s function in a large way.