(For example, while htop is reading /proc/12345/status, it might say "Status: S" because it's sleeping while process 23456 is running.
Instead it must read the status of each process one at a time – which itself takes some CPU time, and during that time other processes may be rescheduled, and the scan may actually miss the running process. on a single-core CPU, htop would only be able to see itself as running.)īut I think the real problem is that htop doesn't actually have the ability to get an "instant" snapshot of the entire system state (at least not on Linux). They cannot all be running at the same time – only one task per CPU core can truly "run", while the rest have to wait until the scheduler gets to them. I noticed that htop showed certain process as consuming CPU, but yet were marked S in the State column (the S column).which meant that the processes were sleeping or idle, but I know they were not sleeping.
0 kommentar(er)
