sudo<\/span> apt<\/span> install<\/span> atop\r\n<\/code><\/pre>\nOther users of Linux have the option to utilize their usual package manager, and then search for the term ‘atop’.<\/p>\n
This directive can exhibit various sensitive system-related details. To avoid any data obfuscation, we can acquire enhanced privileges by utilizing either ‘sudo su’ or ‘sudo -s’. We possess exhaustive documentation regarding sudo.<\/p>\n
The fundamental outcome of the atop Command.<\/h2>\n
To easily view the utilization of system resources at the process level, one option is to execute the ‘atop’ command in the terminal.<\/p>\n
atop\r\n<\/code><\/pre>\n![\"Atop](\"https:\/\/cdn.silicloud.com\/blog-img\/blog\/img\/655cf00ac40ba52feef2bd99\/8-0.png\" "\\"\\"")
<\/div>\nLet’s take a look at the layout, which is divided into two panels. The top panel shows the overall use of the system’s resources, while the bottom panel provides detailed information about each individual process.<\/p>\n
The atop command provides cumulative statistics<\/a>.<\/h3>\nEach item in this perspective concentrates on a specific system resource.<\/p>\n
1. Statistics related to the process.<\/h4>\n\n- PRC – stands for \u201cprocess\u201d.The first two values are the time consumed by the ‘sys’ (system) and ‘user’ processes.
\nIt is followed by the total number of processes as ‘#proc’.
\nThe next value is the number of threads currently running in the system. (‘#trun’)
\n‘#tslpi’ denotes the number of threads that are currently sleeping and interruptible.
\n‘#tslpu’ denotes the number of threads that are currently sleeping and uninterruptible.
\nThe following value is the number of zombie processes.
\nNext up is the number of clone system calls.
\nThe last value is the number of processes that ended during the elapsed time. (‘#exit’)<\/li>\n<\/ul>\n2. Statistics pertaining to performance.<\/h4>\n\n- CPU – relates to CPU utilization.The first two values show the percentage utilization of all the cores by the system and user processes.
\nThe percentage of CPU used for interrupt requests. (‘irq’)
\nThe next value is the idle percentage for all the cores combined.
\nThe following value denotes the waiting each CPU core had to do.
\nNext up is the percentage for the steal time.
\n‘guest’ denotes the guest-percentage, which is the CPU time spent on other virtual machines.
\nThe last two values indicate the current frequency of the CPU.<\/li>\n - Now, the ‘atop’ displays the above statistics for each core independently.<\/li>\n
- CPL – refers to as CPU Load.The first three values are the average loads with different periods: 1, 5, and 15 minutes.
\nThis is followed by the number of context switches (‘csw’)
\nNext up is the number of interrupts (‘intr’)
\nThe last value is number of available CPUs.<\/li>\n<\/ul>\n3. Statistics pertaining to memory.<\/h4>\n\n- MEM – Memory UtilizationThe total physical memory supported.\n
The memory currently free.<\/p>\n
The current cache memory.<\/p>\n
‘buff’ as in \u201cbuffer\u201d is the amount of memory consumed in filesystem meta-data.<\/p>\n
The sum of memory for kernel\u2019s memory allocation shown as ‘slab’.<\/p>\n
The amount of shared memory.<\/li>\n
- SWP – Swap Memory.<\/li>\n<\/ul>\n
3. Statistics related to disks.<\/h4>\n\n- DSK – Disk usageThe first value denotes the percentage of time the system is busy handling requests.
\nThe reading requests issued.
\nThe writing requests issued.
\nThe rate at which data (in KB) is read per reading request.
\nThe rate at which data (in KB) is written per writing request.
\nThe next two values are time rates for reading and writing on the disk in Megabytes.
\nThe last value is the average number of milliseconds spent in handling requests.<\/li>\n<\/ul>\n4. Statistics pertaining to networks<\/h4>\n\n- NET – Network Statistics at the Transport Layer’transport’ signifies the Transport layer in Networking, which deals with the data protocols.
\nThe number of segments received by the system following the TCP protocol. (‘tcpi’)
\nThe number of segments transmitted. (‘tcpo’)
\nThe similar statistics for UCP protocol. (‘udpi’ for UDP in) and (‘udpo’ for UDP out).
\n‘tcpao’ is the number of active TCP open connections.
\nOpposite to previous ‘tcppo’ is the number of passive TCP connections, but still open.
\nThe figure of TCP retransmissions as ‘tcprs’.
\nThe figure of UDP input errors as ‘udpie’.<\/li>\n - NET – Network Statistics at the Network Layer’network’ signifies the Network Layer, which deals with Internet Protocols, IPv4 and IPv6 combined.
\nThe number of IP packets received by the network interfaces. (‘ipi’)
\nThe number of IP packets transmitted out from the interfaces. (‘ipo’)
\nThe quantity of IP packets forwarded to other interfaces. (‘ipfrw’)
\nThe quantity of IP packets delivered. (‘deliv’)
\nThe last two entries are the number of ICMP packets received and transmitted by the network interfaces.<\/li>\n - The following lines refer to each active network interface.The first value is the name of the network interface, like ‘wlp19s0’.
\nThe following two packets are the number of packets that were received and transmitted through the particular interface. (‘pcki’ and ‘pcko’)
\nThe network speed in Megabits (Mbps) as ‘sp’.
\nThe rate at which bits are received and transmitted per second. (‘si’ and ‘so’)
\nThe number of errors in packets received and transmitted. (‘erri’ and ‘erro’).
\nThe last two values are the dropped packets in both ways. (‘drpi’ and ‘drpo’)<\/li>\n<\/ul>\nThe explanation of the top panel of the atop command is now completed.<\/p>\n
Resources allocated to each individual process in a system<\/h3>\n
It is important to note that the values in the ‘atop’ command continually update at specific time intervals.<\/p>\n
For every process entry, the ‘atop’ command’s generic output shows these specific details:<\/p>\n
\n- PID – The process ID.<\/li>\n
- SYSCPU – The amount of CPU consumed by the process while system handling.<\/li>\n
- USRCPU – The amount of CPU consumed by the process, during its running in user mode.<\/li>\n
- VGROW – The amount of virtual memory that the process has occupied since the last value update.<\/li>\n
- RGROW – The amount of resident (physical) memory grown since last value update.<\/li>\n
- RDDSK – The size of data transferred during disk reads.<\/li>\n
- WRDSK – The size of data transferred during disk writes.<\/li>\n
- RUID – The real user ID under which the process is being executed.<\/li>\n
- EUID – The effective user ID under which the process is being executed.<\/li>\n
- ST – The current status of the process.<\/li>\n
- EXC – The exit code after the process terminates<\/li>\n
- THR – The number of threads within the process.<\/li>\n
- S – The current status of the primary thread of the process.<\/li>\n
- CPU – The percentage of CPU utilization of the entire process.<\/li>\n
- CMD – The name of the process.<\/li>\n<\/ul>\n
The processes are arranged according to their CPU usage percentage in this general output. In this specific output, we receive limited information about each system resource type.<\/p>\n
We should attempt to analyze information at the process level for every type of system resource.<\/p>\n
The output generated by the atop command based on memory usage.<\/h2>\n
By utilizing the ‘atop’ command, we have the chance to examine the memory usage of every process operating in the system. This can be achieved by executing the following command:<\/p>\n
atop -m<\/span>\r\n<\/code><\/pre>\n![\"Atop](\"https:\/\/cdn.silicloud.com\/blog-img\/blog\/img\/655cf00ac40ba52feef2bd99\/32-0.png\" "\\"\\"")
<\/div>\nAs evident, the upper panel remains unchanged even after adding the memory option, ‘-m’. Let’s now comprehend the columns for every process entry.<\/p>\n
\n- PID – The process ID.<\/li>\n
- TID – The thread ID.<\/li>\n
- MINFLT – The number of minor page faults that have been solved by accessing data from free pages.<\/li>\n
- MAJFLT – The number of major page faults that have been solved by especially retrieving data from disk.<\/li>\n
- VSTEXT – The virtual memory occupied by the process text.<\/li>\n
- VSLIBS – The virtual memory occupied by the shared libraries of the process.<\/li>\n
- VDATA – The virtual memory size of the private data of the process.<\/li>\n
- VSTACK – The virtual memory size of the private stack of the process.<\/li>\n
- VSIZE – The total virtual memory size of the process.<\/li>\n
- RSIZE – The total resident memory occupied by the process.<\/li>\n
- MEM – The percentage of RAM consumed by the process.<\/li>\n<\/ul>\n
The ‘MEM’ column determines the sorting order of the processes.<\/p>\n
As ‘atop’ is an interactive command utility, we can modify the columns directly within the program. To access memory-specific output, we simply need to enter ‘m’ while ‘atop’ is displaying information in the terminal.<\/p><\/blockquote>\n
Generating output specific to a disk by utilizing the atom command in Linux.<\/h2>\n
We can utilize the ‘-d’ option in conjunction with the ‘atop’ command to gather disk usage information.<\/p>\n
atop -d<\/span>\r\n<\/code><\/pre>\n![\"Atop](\"https:\/\/cdn.silicloud.com\/blog-img\/blog\/img\/655cf00ac40ba52feef2bd99\/40-0.png\" "\\"\\"")
<\/div>\nIn the output that specifically refers to the disk, there isn’t much noteworthy information. However, a couple of significant observations are:<\/p>\n
\n- RDDSK – The size of data transferred during disk reads.<\/li>\n
- WRDSK – The size of data transferred during disk writes.<\/li>\n
- WCANCL – The size of data initially written, but later withdrawn<\/li>\n
- DSK – The percentage of Disk occupied.<\/li>\n
- CMD – The name of the process.<\/li>\n<\/ul>\n
It is important to mention that the processes are organized according to the ‘DSK’ column.<\/p>\n
Discover Background Processes using the atop command.<\/h2>\n
The information presented to us in the command line output format is a list of the commands running in the background as processes.<\/p>\n
atop -c<\/span>\r\n<\/code><\/pre>\n![\"Atop](\"https:\/\/cdn.silicloud.com\/blog-img\/blog\/img\/655cf00ac40ba52feef2bd99\/47-0.png\" "\\"\\"")
<\/div>\nYou can rerun the same process by copying and pasting the lines from the command line column. This output provides us with the precise command that was executed in the background to start the process.<\/p>\n
Information organized in a thread-based format.<\/h2>\n
In addition to examining process data, the atop command allows for monitoring resource usage at the thread level. To view this information, we have two options:<\/p>\n
atop -y<\/span>\r\n<\/code><\/pre>\nSimply press the ‘y’ key if the command is already showing system resource information.<\/p>\n
![\"Atop](\"https:\/\/cdn.silicloud.com\/blog-img\/blog\/img\/655cf00ac40ba52feef2bd99\/53-0.png\" "\\"\\"")
<\/div>\nIt is evident that there have been no modifications to any of the columns related to system resources. The only addition is the thread count for each corresponding process.<\/p>\n
Other random details<\/h2>\n
The ‘atop’ command provides a variety of information that can be extracted, and among the helpful ones are:<\/p>\n
Discovering the commencement moments of processes.<\/h3>\n
2. Locate the initiations of processes.<\/p>\n
3. Identify when processes begin.<\/p>\n
4. Uncover the starting times of processes.<\/p>\n
By utilizing the ‘-v’ option, we can obtain the attributes of the process.<\/p>\n
atop -v<\/span>\r\n<\/code><\/pre>\n![\"Atop](\"https:\/\/cdn.silicloud.com\/blog-img\/blog\/img\/655cf00ac40ba52feef2bd99\/60-0.png\" "\\"\\"")
<\/div>\n2. Count of the system’s processes per user.<\/h3>\natop -au<\/span>\r\n<\/code><\/pre>\n![\"Atop](\"https:\/\/cdn.silicloud.com\/blog-img\/blog\/img\/655cf00ac40ba52feef2bd99\/63-0.png\" "\\"\\"")
<\/div>\nWhich core is the process currently operating on?<\/h3>\n
The scheduling characteristics for a process can be found by using the ‘-s’ option.<\/p>\n
atop -s<\/span>\r\n<\/code><\/pre>\n![\"Atop](\"https:\/\/cdn.silicloud.com\/blog-img\/blog\/img\/655cf00ac40ba52feef2bd99\/67-0.png\" "\\"\\"")
<\/div>\nA couple of impressive stunts at the top<\/h2>\n
There are a few ‘atop’ command hacks that could come in handy.<\/p>\n
\n- Pausing the ‘atop’ screen – using ‘z’ key.<\/li>\n
- Changing the time interval of value updates – using ‘i’ key followed by the number of seconds, we wish to change it to.<\/li>\n
- Interrupt to instantly update the values – using ‘t’ key.<\/li>\n
- Quitting the display – using ‘q’ key.<\/li>\n<\/ul>\n
In summary,<\/h2>\n
We are aware that the ‘atop’ command can be overwhelming for Linux users. Mastering this exceptional command requires dedication and determination. If you have any questions, feel free to reach out to us in the comments section.<\/p>\n
<\/p>\n
<\/p>\n
more tutorials<\/p>\n
Partition in Linux Step-by-Step Guide(Opens in a new browser tab)<\/span><\/a><\/p>\nautomatic scaling of Kubernetes pods using Metrics Server?(Opens in a new browser tab)<\/span><\/a><\/p>\nmultithreading in Java that you need to know(Opens in a new browser tab)<\/span><\/a><\/p>\nAdding a string to a Python variable(Opens in a new browser tab)<\/span><\/a><\/p>\n