Resource Monitor allows you to monitor the CPU usage, memory usage, disk utilization and network flow. You can choose to monitor in real time or view previous data.
Resource Monitor allows you to monitor the CPU usage, memory usage and network flow. You can choose to monitor in real time or view previous data.
Click on Performance tab to view the resource utilization data. Detailed date, time and information of the chart will be shown upon mouseover.
You can see the overall CPU usage of User, System and I/O Wait. CPU load could be high when Resource Monitor is first launched, because the system needs to collect its resource data and load the UI page at the same time.
User shows the percentage of CPU used to run user applications. System shows the percentage of CPU used in the core of the system, hardware/software IRQs. I/O Wait shows the percentage of CPU spent on I/O wait.
Utilization is the sum of User and System CPU usage.
The Load Average within 1, 5, and 15 minutes is displayed, showing the run-queue length (i.e. the sum of the number of processes that are currently running plus the number that are waiting to run).
I/O wait is a normal behavior. Since the speed of CPU is far faster than that of I/O, it is common for CPU to wait for the transmission of disks or network to complete. However, if the percentage of I/O wait is extremely large, it means that the CPU spends most of the time on I/O wait and might not be well utilized. You can use more efficient disk group configurations (e.g. SHR or RAID 5) or network configurations (e.g. Bonding) to achieve better system performance.
The overall memory usage of physical memory and swap space will be shown. Memory usage remains high because the system stores frequently accessed data in cache, so the data can be quickly obtained without accessing the hard disk. Cache memory will be released when overall memory is insufficient.
High swap space usage indicates insufficient system memory, and will also affect the system performance. You can view the rate of swap in and swap out by choosing Swap from the drop-down menu on the top.
The network flow chart displays sent and received data in KB's per second. If PPPoE is connected, its transfer rate will also show up on the chart.
You can choose to view the overall disk utilization, transfer rate or IOPS by clicking the drop-down menu at the top of the chart. You can click View All at the bottom to select more disks by ticking the checkboxes to add their data to the chart.
This page displays the overall transfer status of volumes. Click the drop-down menu above the chart to view transfer utilization, transfer rate, or IOPS. Click the View All button to select individual volumes and add them to the chart.
This page displays the overall status of currently running iSCSI LUNs. Click the drop-down menu above the chart to select a LUN and view its status. Three charts are displayed by default, which are Throughput, IOPS and Latency. For more detailed information, click the Choose Charts button to select other charts that you want to view.
Click on Process tab to view the CPU and memory usage of each process in the order of decreasing CPU load.
The process Status includes Running, Sleeping and Stopped. Linux equivalents of process status are running, stopped/tracing, sleeping.
Sleeping can be followed by a letter for detailed information, e.g. 'D' for disk sleep, 'Z' for zombie, 'X' for dead.
On this tab, you can view and manage the clients who are currently connected to the system and accessing resources. This section displays clients that are connected via HTTP, TELNET, SSH, SMB/CIFS, AFP, FTP, and NFS.
Under the Speed Limit tab, you can view and manage the list of file transfer processes that applied speed limit on DiskStation.
Click Refresh to reload the page and get the most updated records.
Click Kill connection to stop the file transfer. You will have to start the file transfer again to complete the process successfully.
Click Settings to set up following options:
Click Apply to save the settings.
Performance alarms will operate through the following mechanism to minimize false alarms and to prevent excessive consumption of system resources within a short period of time.
Therefore, for one single event, an alarm will at latest be triggered 450 seconds after the first detection of the event.
Performance alarms will trigger different actions depending on the alarm levels.
Logs of performance alarms can be viewed at the Performance Alarm tab or DSM's Log Center.