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.
On massive multi-core systems (more than 128 cores), even the aggregation on 4 columns makes it impossible to view effectively the process panel as the full space is used for displaying the core usage.
One way to mitigate that is to restrict the view to Average CPU (F2 - delete "CPU (1&2)/4" and "CPU (3&4)/4") translating in the following change in ~/.config/htop/htoprc:
Yet this average view is of less interest for debugging parallel jobs / processes and quickly review tasks affinity etc: there should be an intermediate solution between the detailed core view and the aggregation on a single bar.
So would it be possible to offer more options for aggregation of the meter (currently at max 4 columns-- could we imagine for instance going on 8 columns and/or aggregate statistics of 2 cores per line for instance ?
The text was updated successfully, but these errors were encountered:
On massive multi-core systems (more than 128 cores), even the aggregation on 4 columns makes it impossible to view effectively the process panel as the full space is used for displaying the core usage.
One way to mitigate that is to restrict the view to Average CPU (F2 - delete "CPU (1&2)/4" and "CPU (3&4)/4") translating in the following change in
~/.config/htop/htoprc
:Yet this average view is of less interest for debugging parallel jobs / processes and quickly review tasks affinity etc: there should be an intermediate solution between the detailed core view and the aggregation on a single bar.
So would it be possible to offer more options for aggregation of the meter (currently at max 4 columns-- could we imagine for instance going on 8 columns and/or aggregate statistics of 2 cores per line for instance ?
The text was updated successfully, but these errors were encountered: