On Mon, Mar 24, 2025 at 06:00:48PM -0400, Ted Unangst wrote:
> On 2025-03-23, Ted Unangst wrote:
> > On 2025-03-23, Job Snijders wrote:
> > > Did you consider cranking it up to 7 digits (to better accommodate
> > > chubby instances of for example chromium, mount_mfs, and mutt)?
> > 
> > I think a better fix is to dynamically size some columns, but this
> > is a bit more involved giving the way the printing code works. Will
> > think about it for a bit.
> 
> So I'm not wedded to this idea, but if the terminal is wider, we can
> make a few adjustments. You want to see big processes, you need to buy
> a bigger monitor.

It certainly aligns the columns in the output nicer:

OLD:
$ ps aux | grep -e RSS -e mfs
USER       PID %CPU %MEM    VSZ    RSS TT  STAT   STARTED       TIME COMMAND
root     56978  0.0  1.0 7865236 415276 ??  S      12:21PM    0:07.64 /sbin/mount_mfs -o rw -o nodev -o nosuid -o async -s7.5G swap /tmp
job      94733  0.0  0.0    796   1280 p3  S+p     4:16PM    0:00.00 grep -e RSS -e mfs

NEW:
$ ./obj/ps aux | grep -e RSS -e mfs
USER       PID %CPU %MEM      VSZ      RSS TT  STAT   STARTED       TIME COMMAND
root     56978  0.0  1.0  7865236   415276 ??  S      12:21PM    0:07.64 /sbin/mount_mfs -o rw -o nodev -o nosuid -o async -s7.5G swap /tmp
job      49380  0.0  0.0      800     1288 p3  S+p     4:16PM    0:00.00 grep -e RSS -e mfs

However it seems the VSZ and RSS column can be shrunk by 1 character:

PROPOSED:
$ ./obj/ps aux | grep -e RSS -e mfs
USER       PID %CPU %MEM     VSZ     RSS TT  STAT   STARTED       TIME COMMAND
root     56978  0.0  1.0 7865236  415276 ??  S      12:21PM    0:07.66 /sbin/mount_mfs -o rw -o nodev -o nosuid -o async -s7.5G swap /tmp
job      10922  0.0  0.0     796    1272 p3  S+p     4:21PM    0:00.00 grep -e RSS -e mfs

Is there a reason you proposed +=2 instead of +=1? Preparation for 10GB+
processes? Maybe VSZ/RSS column width should be set not just based on the
availability of a bigger monitor, but also the maximum VSZ/RSS value?

Kind regards,

Job