Return to Answer

The other answer described well what's sugov:0, so let me explain further the nature of the displayed %CPU values.

Whatever top(1) or htop(1) report about the percentage of CPU usage is the current state. Thus, if some process or kernel thread uses a certain CPU percentage, that's the case at that very moment, while the very next moment it may use 0% or an ever higher percentage. That's also how bursty or short-lived loads can hide from top(1) or htop(1).

in general, it's much better to get the sense of CPU usage by checking the values in the TIME column in the output of ps(1), in particular ps axuw, becase it accounts for the history of CPU usage for each process since the system has booted up. The TIME column can also be added to what top(1) displays, which is what I have in place with htop(1), for example.

However, short-lived processes can also hide from their exposure through the TIME columns, but that doesn't apply to the question.

The other answer described well what's sugov:0, so let me explain further the nature of the displayed %CPU values.

Whatever top(1) or htop(1) report about the percentage of CPU usage is the current state. Thus, if some process or kernel thread uses a certain CPU percentage, that's the case at that very moment, while the very next moment it may use 0% or an ever higher percentage. That's also how bursty or short-lived loads can hide from top(1) or htop(1).

in general, it's much better to get the sense of CPU usage by checking the values in the TIME column in the output of ps(1), in particular ps axuw, becase it accounts for the history of CPU usage for each process since the system has booted up. The TIME column can also be added to what top(1) displays, which is what I have in place with htop(1), for example.

However, short-lived processes can also hide from their exposure through the TIME columns, but that doesn't apply to the question.

The other answer described well what's sugov:0, so let me explain further the nature of the displayed %CPU values.

Whatever top(1) or htop(1) report about the percentage of CPU usage is the current state. Thus, if some process or kernel thread uses a certain CPU percentage, that's the case at that very moment, while the very next moment it may use 0% or an ever higher percentage. That's also how bursty or short-lived loads can hide from top(1) or htop(1).

in general, it's better to check the values in the TIME column in the output of ps axuw, becase it accounts for the history of CPU usage for each process since the system was booted up. The TIME column can also be added to what top(1) displays, which is what I have in place with htop(1), for example.

However, short-lived processes can also hide from their exposure through the TIME columns, but that doesn't apply to the question.

The other answer described well what's sugov:0, so let me explain further the nature of the displayed %CPU values.

Whatever top(1) or htop(1) report about the percentage of CPU usage is the current state. Thus, if some process or kernel thread uses a certain CPU percentage, that's the case at that very moment, while the very next moment it may use 0% or an ever higher percentage. That's also how bursty or short-lived loads can hide from top(1) or htop(1).

in general, it's much better to get the sense of CPU usage by checking the values in the TIME column in the output of ps(1), in particular ps axuw, becase it accounts for the history of CPU usage for each process since the system has booted up. The TIME column can also be added to what top(1) displays, which is what I have in place with htop(1), for example.

However, short-lived processes can also hide from their exposure through the TIME columns, but that doesn't apply to the question.

The other answer described well what's sugov:0, so let me explain further the nature of the displayed %CPU values.

Whatever top(1) or htop(1) report about the percentage of CPU usage is the current state. Thus, if some process or kernel thread uses a certain CPU percentage, that's the case at that very moment, while the very next moment it may use 0% or an ever higher percentage. That's also how bursty or short-lived loads can hide from top(1) or htop(1).

in general, it's better to check the values in the TIME column in the output of ps axuw, becase it accounts for the history of CPU usage for each process since the system was booted up. The TIME column can also be added to what top(1) displays, which is what I have in place with htop(1), for example.

The other answer described well what's sugov:0, so let me explain further the nature of the displayed %CPU values.

Whatever top(1) or htop(1) report about the percentage of CPU usage is the current state. Thus, if some process or kernel thread uses a certain CPU percentage, that's the case at that very moment, while the very next moment it may use 0% or an ever higher percentage. That's also how bursty or short-lived loads can hide from top(1) or htop(1).

in general, it's better to check the values in the TIME column in the output of ps axuw, becase it accounts for the history of CPU usage for each process since the system was booted up. The TIME column can also be added to what top(1) displays, which is what I have in place with htop(1), for example.

However, short-lived processes can also hide from their exposure through the TIME columns, but that doesn't apply to the question.