I love htop. But I can't figure out a way to disable the CPU monitors. I use a machine with 768 cores which makes it kind of useless.
Htop Explained Visually
21–30 of 41 posts
Re: Htop Explained Visually
#22I love htop. But I can't figure out a way to disable the CPU monitors. I use a machine with 768 cores which makes it kind of useless.
Re: Htop Explained Visually
#23I love htop. But I can't figure out a way to disable the CPU monitors. I use a machine with 768 cores which makes it kind of useless.
Re: Htop Explained Visually
#24I love htop. But I can't figure out a way to disable the CPU monitors. I use a machine with 768 cores which makes it kind of useless.
left_meters=AllCPUs Memory Swap
to be left_meters=CPU Memory Swap
That will replace the default CPU monitor with a single meter for the average across all cores. After that, you'll be able to customize things the standard way by pressing F2 within htop.Re: Htop Explained Visually
#25As a consequence of trying htop after a long time, I got a reminder that VIRT is not related to RES. I noticed Libreoffice Calc with 29.7 GB of virtual memory and only 198 MB actually used. I wonder why LO made a malloc of nearly 30 GB, but memory is cheap especially because it's virtual. The next one on the list is Firefox with 8.5 GB VIRT and 994 MB RES. By the way, I've got 16 GB of RAM and no swap. Anyway all tha…
smem's measures - USS, unqiue set size (unshared pages) and PSS, proportional set size (shared pages divided by their share count, ie. how many tasks share them), are far more accurate and easier to reason about than RSS and VSS.
Re: Htop Explained Visually
#26Why is it "Tasks" at the top right? Shouldn't it be "Processes"?
If you have their display enabled htop will divide them down as well.
Re: Htop Explained Visually
#27As a consequence of trying htop after a long time, I got a reminder that VIRT is not related to RES. I noticed Libreoffice Calc with 29.7 GB of virtual memory and only 198 MB actually used. I wonder why LO made a malloc of nearly 30 GB, but memory is cheap especially because it's virtual. The next one on the list is Firefox with 8.5 GB VIRT and 994 MB RES. By the way, I've got 16 GB of RAM and no swap. Anyway all tha…
RES isn't physical memory, either. I can happily have, say, 30 GB RES on a system with only 1 GB RAM (and no swap). smem's measures - USS, unqiue set size (unshared pages) and PSS, proportional set size (shared pages divided by their share count, ie. how many tasks share them), are far more accurate and easier to reason about than RSS and VSS.
If I have a process that says it's using 1GB of RES, then you can guarantee there is at least 1GB of physical memory in use. It just might also be in use by other things also reporting their own RES usage.
Re: Htop Explained Visually
#28Re: Htop Explained Visually
#29what are units of load average?
1.0 = 100% usage of a 1-core system
1.0 = 50% usage of a 2-core system
4.0 = 50% usage of an 8-core system
8.0 = 100% usage of an 8-core system
And IIRC, load average is represented usually as 3 numbers, which are over the last 5, 10, and 15 minutes.Re: Htop Explained Visually
#30Htop is the first software I install on any new server. Just wished that they made iotop as awesome as htop :D