From owner-freebsd-questions Tue Apr 24 21:40:22 2001 Delivered-To: freebsd-questions@freebsd.org Received: from fremont.bolingbroke.com (adsl-216-102-90-210.dsl.snfc21.pacbell.net [216.102.90.210]) by hub.freebsd.org (Postfix) with ESMTP id DEA9337B629 for ; Tue, 24 Apr 2001 21:40:18 -0700 (PDT) (envelope-from hacker@bolingbroke.com) Received: from fremont.bolingbroke.com (fremont.bolingbroke.com [216.102.90.210]) by fremont.bolingbroke.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f3P4eGe55359; Tue, 24 Apr 2001 21:40:16 -0700 (PDT) Date: Tue, 24 Apr 2001 21:40:16 -0700 (PDT) From: Ken Bolingbroke To: Jorge Biquez Cc: freebsd-questions@FreeBSD.ORG Subject: Re: System Usage... In-Reply-To: <5.0.2.1.2.20010424194509.03b3b100@icsmx.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 24 Apr 2001, Jorge Biquez wrote: > 2) How could I know that my system is overloaded?. Because of the use of > Memory? or Active process? idle percentage? use of swap memory? Personally, my definition of overloaded is more holoistic than looking at any one or set of metrics. If the machine is doing what it's supposed to do in a timely manner, then it's not overloaded. If the load is such that it's causing things to fail or responding too slowly, then it's overloaded. You could be out of RAM and using swap, but still doing everything the machine needs to do with a good response time, so the usage of RAM isn't a definite factor. Ditto for active processes, idle CPU, etc. Each of those metrics will react differently depending on what you're doing with the machine, anyway. Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message