they are displayable with the ‘f’ (Fields Management)
interactive command.
Any field is selectable as the sort field, and you control whether they are sorted high‐to‐low or low‐to‐high. For additional information on sort provisions see topic 4c. TASK AREA Commands, SORTING.
The fields related to physical memory or virtual memory reference ‘(KiB)’ which is the unsuffixed display mode. Such fields may, however, be scaled from KiB through PiB. That scaling is influenced via the ‘e’
interactive command or established for startup through a build option.
%CPU -- CPU Usage
The task’s share of the elapsed CPU time since the last screen update, expressed as a percentage of total CPU time.
In a true SMP environment, if a process is multi‐threaded and top is not operating in Threads mode, amounts greater than 100% may be reported. You toggle Threads mode with the ‘H’ interactive command.
Also for multi‐processor environments, if Irix mode is Off, top will operate in Solaris mode where a task’s cpu usage will be divided by the total number of CPUs. You toggle Irix/Solaris modes with the ‘I’
interactive command.
Note: When running in forest view mode (‘V’) with children collapsed (‘v’), this field will also include the CPU time of those unseen children. See topic 4c. TASK AREA Commands, CONTENT for more information
regarding the ‘V’ and ‘v’ toggles.
%CUC -- CPU Utilization
This field is identical to %CUU below, except the percentage also reflects reaped child processes.
%CUU -- CPU Utilization
A task’s total CPU usage divided by its elapsed running time, expressed as a percentage.
If a process currently displays high CPU usage, this field can help determine if such behavior is normal. Conversely, if a process has low CPU usage currently, %CUU may reflect historically higher demands over
its lifetime.
%MEM -- Memory Usage (RES)
A task’s currently resident share of available physical memory.
See ‘OVERVIEW, Linux Memory Types’ for additional details.
AGID -- Autogroup Identifier
The autogroup identifier associated with a process. This feature operates in conjunction with the CFS scheduler to improve interactive desktop performance.
When /proc/sys/kernel/sched_autogroup_enabled is set, a new autogroup is created with each new session (see SID). All subsequently forked processes in that session inherit membership in this autogroup. The
kernel then attempts to equalize distribution of CPU cycles across such groups. Thus, an autogroup with many CPU intensive processes (e.g make ‐j) will not dominate an autogroup with only one or two processes.
When ‐1 is displayed it means this information is not available.
AGNI -- Autogroup Nice Value
The autogroup nice value which affects scheduling of all processes in that group. A negative nice value means higher priority, whereas a positive nice value means lower priority.
CGNAME -- Control Group Name
The name of the control group to which a process belongs, or ‘-’ if not applicable for that process.
This will typically be the last entry in the full list of control groups as shown under the next heading (CGROUPS). And as is true there, this field is also variable width.
CGROUPS -- Control Groups
The names of the control group(s) to which a process belongs, or ‘-’ if not applicable for that process.
Control Groups provide for allocating resources (cpu, memory, network bandwidth, etc.) among installation‐defined groups of processes. They enable fine‐grained control over allocating, denying, prioritizing,
managing and monitoring those resources.
Many different hierarchies of cgroups can exist simultaneously