Alat Kinerja Memori dan CPU

Understanding system performance is key to troubleshooting slow applications or an unresponsive server. CPU and memory are often the first resources to check.

In this lesson, we'll explore powerful command-line tools to monitor and diagnose issues related to your system's CPU and memory usage.

The vmstat (virtual memory statistics) command provides a quick, real-time snapshot of your system's activity. It reports on processes, memory, paging, block I/O, traps, and CPU activity.

It's excellent for observing current system behavior and identifying immediate bottlenecks.

Let's run vmstat 1 1 to see a single report, then we'll break down the memory-related output. This command shows a report every 1 second, for 1 iteration.

• swpd: amount of virtual memory used.
• free: amount of idle memory.
• buff: memory used as buffers.
• cache: memory used as cache.

Now, let's look at the CPU section of vmstat. Run the command again if you like, and focus on the 'cpu' columns:

• us (user): time spent running non-kernel code.
• sy (system): time spent running kernel code.
• id (idle): time spent idle.
• wa (wait): time spent waiting for I/O.

High wa often indicates disk bottlenecks.

The sar (System Activity Reporter) command is part of the sysstat package. Unlike vmstat, sar can collect and report historical system activity data.

This makes it invaluable for long-term analysis, identifying trends, and diagnosing intermittent problems that might not be visible with real-time tools.

To view CPU utilization with sar, we use the -u option. Run sar -u 1 1 to get a single report.

• %user: CPU usage by user-level applications.
• %system: CPU usage by kernel-level tasks.
• %iowait: Time CPU spent waiting for I/O.
• %idle: Time CPU was idle.

To get detailed memory utilization reports with sar, use the -r option. Try sar -r 1 1.

• kbmemfree: Amount of free memory.
• kbmemused: Amount of used memory.
• %memused: Percentage of used memory.
• kbbuffers: Memory used by kernel buffers.
• kbcached: Memory used by page cache.

The mpstat (multi-processor statistics) command is also part of the sysstat package. Its main advantage is providing per-processor or per-core CPU activity.

This is crucial for systems with multiple CPU cores, as it helps identify if a specific core is overloaded while others are idle.

To see statistics for all individual CPU cores, use mpstat -P ALL 1 1. You'll see a separate line for each core (CPU 0, CPU 1, etc.) and an 'all' line for the average.

This helps pinpoint if a single-threaded application is maxing out one core, even if overall CPU usage seems low.

Which of the following statements about Linux performance tools are TRUE?

In this lesson, you learned about three essential tools for monitoring CPU and memory performance:

• vmstat: For real-time system activity snapshots.
• sar: For collecting and reporting historical system activity data.
• mpstat: For detailed per-processor/per-core CPU usage.

Mastering these commands will significantly boost your ability to diagnose and troubleshoot Linux system performance issues.