You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 8, 2020. It is now read-only.
Directly after starting htop, I always see a CPU utilization of 100 % on one core that comes from, well, starting htop. I only see the CPU utilisations that interest me after one second, when the program reloads the values
I think this is a bit suboptimal, as I guess people are generally not interested in the brief utilisation from starting htop. It would be nice if the measurement were made e.g. with a small delay that avoids showing this result. Given the number of people using htop, I guess increasing their convenience for one second every time they use it is worth it.
The text was updated successfully, but these errors were encountered:
Directly after starting htop, I always see a CPU utilization of 100 % on one core that comes from, well, starting htop. I only see the CPU utilisations that interest me after one second, when the program reloads the values
I think this is a bit suboptimal, as I guess people are generally not interested in the brief utilisation from starting htop. It would be nice if the measurement were made e.g. with a small delay that avoids showing this result. Given the number of people using htop, I guess increasing their convenience for one second every time they use it is worth it.
The text was updated successfully, but these errors were encountered: