Aqui está um exemplo de saída de top :
top - 14:21:40 up 7 days, 21:57, 7 users, load average: 0.13, 0.04, 0.04
Tasks: 107 total, 2 running, 105 sleeping, 0 stopped, 0 zombie
Cpu0 : 1.0% us, 1.0% sy, 0.0% ni, 96.1% id, 1.9% wa, 0.0% hi, 0.0% si
Cpu1 : 1.0% us, 1.0% sy, 0.0% ni, 98.0% id, 0.0% wa, 0.0% hi, 0.0% si
Mem: 2050756k total, 2034236k used, 16520k free, 22252k buffers
Swap: 2097144k total, 87108k used, 2010036k free, 1609212k cached
- A primeira linha é facilmente interpretada, somente porque há três diferentes médias de carga não é óbvia: esses valores usam três escalas de tempo diferentes.
- Segunda linha: resumo das tarefas, agrupadas por seu estado
-
A linha da CPU tem dois modos, ou
Cpu(s): 1.0% us, 0.5% sy, 0.0% ni, 98.5% id, 0.0% wa, 0.0% hi, 0.0% sionde todos os núcleos de CPU são resumidos ou semelhantes no exemplo acima, onde cada núcleo tem sua própria linha. Você pode alternar entre estes modos com 1 . Cada núcleo pode ser usado para 100%, portanto, com dois núcleos, o valor máximo total é de 200%.
As abreviaturas de duas letras estão em negrito na lista a seguir (c & p de uma resposta anterior ):
- user: normal processes executing in user mode
- nice: niced processes executing in user mode
- system: processes executing in kernel mode
- idle: twiddling thumbs
- iowait: waiting for I/O to complete
- irq: servicing interrupts [hard interrupts hi]
- softirq: servicing softirqs [soft interrupts si]
- steal: involuntary wait
-
Mem e Swap são para RAM física e espaço de troca, respectivamente.
-
A lista de processos é explicada em detalhes na página man do top ( 2a. DESCRIPTIONS of Fields ). Como seu man page parece incompleto, abaixo está um trecho; também há cópias da man page completa na internet . Por padrão, essas colunas são mostradas (personalize com f ):
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMANDPara resolver sua questão específica sobre o uso da CPU: Se um processo é executado em paralelo, ou seja, pode usar vários núcleos de CPU, um uso de 400% indica que 4 núcleos são usados completamente.
PID -- Process Id: The task's unique process ID, which periodically wraps, though never restarting at zero.
PPID -- Parent Process Pid: The process ID of a task's parent.
RUSER -- Real User Name: The real user name of the task's owner.
UID -- User Id: The effective user ID of the task's owner. Blockquote
USER -- User Name: The effective user name of the task's owner.
GROUP -- Group Name: The effective group name of the task's owner.
TTY -- Controlling Tty: The name of the controlling terminal. This is usually the device (serial port, pty, etc.) from which the process was started, and which it uses for input or output. However, a task need not be associated with a terminal, in which case you'll see '?' displayed.
PR -- Priority: The priority of the task.
NI -- Nice value: The nice value of the task. A negative nice value means higher priority, whereas a positive nice value means lower priority. Zero in this field simply means priority will not be adjusted in determining a task's dispatchability.
P -- Last used CPU (SMP): A number representing the last used processor. In a true SMP environment this will likely change frequently since the kernel inten- tionally uses weak affinity. Also, the very act of running top may break this weak affinity and cause more processes to change CPUs more often (because of the extra demand for cpu time).
%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 '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.
TIME -- CPU Time: Total CPU time the task has used since it started. When 'Cumulative mode' is On, each process is listed with the cpu time that it and its dead children has used. You toggle 'Cumulative mode' with 'S', which is a command-line option and an interactive command. See the 'S' interactive command for additional information regarding this mode.
TIME+ -- CPU Time, hundredths: The same as 'TIME', but reflecting more granularity through hundredths of a second.
%MEM -- Memory usage (RES): A task's currently used share of available physical memory.
VIRT -- Virtual Image (kb): The total amount of virtual memory used by the task. It includes all code, data and shared libraries plus pages that have been swapped out.
VIRT = SWAP + RESSWAP -- Swapped size (kb): The swapped out portion of a task's total virtual memory image.
RES -- Resident size (kb): The non-swapped physical memory a task has used.
RES = CODE + DATACODE -- Code size (kb): The amount of physical memory devoted to executable code, also known as the 'text resident set' size or TRS.
DATA -- Data+Stack size (kb): The amount of physical memory devoted to other than executable code, also known as the 'data resident set' size or DRS.
SHR -- Shared Mem size (kb): The amount of shared memory used by a task. It simply reflects memory that could be potentially shared with other processes.
nFLT -- Page Fault count: The number of major page faults that have occurred for a task. A page fault occurs when a process attempts to read from or write to a virtual page that is not currently present in its address space. A major page fault is when disk access is involved in making that page available.
nDRT -- Dirty Pages count: The number of pages that have been modified since they were last written to disk. Dirty pages must be written to disk before the cor- responding physical memory location can be used for some other virtual page.
S -- Process Status The status of the task which can be one of: D = uninterruptible sleep, R = running, S = sleeping, T = traced or stopped, Z = zombie. Tasks shown as running should be more properly thought of as 'ready to run' -- their task_struct is simply represented on the Linux run-queue. Even without a true SMP machine, you may see numerous tasks in this state depending on top's delay interval and nice value.
Command -- Command line or Program name: Display the command line used to start a task or the name of the associated program. You toggle between command line and name with 'c', which is both a command-line option and an interactive command. When you've chosen to display command lines, processes without a command line (like kernel threads) will be shown with only the pro- gram name in parentheses, as in this example: ( mdrecoveryd ) Either form of display is subject to potential truncation if it's too long to fit in this field's current width. That width depends upon other fields selected, their order and the current screen width. Note: The 'Command' field/column is unique, in that it is not fixed-width. When displayed, this column will be allocated all remain- ing screen width (up to the maximum 512 characters) to provide for the potential growth of program names into command lines.
WCHAN -- Sleeping in Function: Depending on the availability of the kernel link map ('System.map'), this field will show the name or the address of the kernel func- tion in which the task is currently sleeping. Running tasks will display a dash ('-') in this column. Note: By displaying this field, top's own working set will be increased by over 700Kb. Your only means of reducing that overhead will be to stop and restart top.
Flags -- Task Flags: This column represents the task's current scheduling flags which are expressed in hexadecimal notation and with zeros suppressed. These flags are officially documented in . Less formal documentation can also be found on the 'Fields select' and 'Order fields' screens.