ok...so we all know that top(1) cannot compute the exact CPU usage for all processes, since some processes get spawned and exit so fast that they don't fall into the calculation range. i think nobody is getting angry when top(1) is off by a few percent. however please take a look at the following top(1) output. this is just ridiculous! out of 800% of CPU power, almost 600% mysteriously vanished. is there really nothing to improve top(1)'s behaviour when the CPU is dealing with a lot of short processes (time wise) with a hugh CPU burst? this output was gathered on HEAD (r227491) running on i386. cheers. alex ps: no, switching between raw and weighted CPU stats did *not* make a difference. ;)
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:22 UTC