top: added some elapsed running time 'ELAPSED' support
When the 'STARTED' field was added, in the message for
the commit referenced below, I explained why 'ELAPSED'
shouldn't be implemented though it might be preferred.
Well, after climbing out of my box to do a little more
thinking, I came up with the way to add that 'ELAPSED'
field while avoiding the possible performance penalty.
Just do not show what would change with every refresh!
If we do not show the seconds portion of a scaled tics
amount then the problem goes away. And this comes with
an additional benefit. The HH,MM (hours,minutes) style
then is readily compared with that system uptime shown
as HH:MM. The only difference is just the comma/colon.
[ assuming the top uptime/load average toggle was on ]
Reference(s):
. introduced 'start time' field
commit 7647e96b0a
Signed-off-by: Jim Warner <james.warner@comcast.net>
This commit is contained in:
@@ -746,6 +746,14 @@ included in the \*(MV (VIRT) amount.
|
||||
|
||||
\*(XX.
|
||||
|
||||
.TP 4
|
||||
\fBELAPSED \*(Em Elapsed Running Time\fR
|
||||
The length of time since a process was started.
|
||||
Thus, the most recently started task will display the smallest time interval.
|
||||
|
||||
The value will be expressed as 'HH,MM' (hours,minutes) but is subject to
|
||||
additional scaling if the interval becomes too great to fit column width.
|
||||
|
||||
.TP 4
|
||||
\fBENVIRON \*(Em Environment variables \fR
|
||||
Display all of the environment variables, if any, as seen by the
|
||||
|
Reference in New Issue
Block a user