Date: Mon, 4 Oct 1999 17:35:43 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: Greg Lehey <grog@lemis.com> Cc: Dag-Erling Smorgrav <des@flood.ping.uio.no>, thyerm@camtech.net.au, Ruslan Ermilov <ru@FreeBSD.ORG>, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: top with < 1 second delay (was: cvs commit: src/bin/sleep sleep.1 sleep.c) Message-ID: <199910050035.RAA72855@apollo.backplane.com> References: <Pine.BSF.4.10.9910042220480.308-100000@localhost> <xzp670n88c7.fsf@flood.ping.uio.no> <199910041635.JAA67276@apollo.backplane.com> <19991005091744.W40186@freebie.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
:>>
:>> Dag-Erling Smorgrav - des@flood.ping.uio.no
:>
:> top is kinda cpu-heavy. Occassionally I'll use 's0<return>' just to
:> watch the display go nuts, but beyond the laughs having a less then
:> one second update time isn't all that useful for top.
:
:I think that depends on what you're looking at. I could imagine that
:people look at other things besides the CPU time breakdown. I
:personally think that it would be a useful thing to have.
:
:Greg
Well, as I said, top can be very cpu-heavy, especially on machines
with a lot of processes. So if you are going to allow < 1 second
top the feature should be restricted to root.
systat, vmstat, and iostat are not cpu-heavy and one could allow
< 1 second operation with those programs without the root restriction,
though I would impose a 1/10 second minimum.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199910050035.RAA72855>