From owner-freebsd-questions Tue Mar 12 12:28:50 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA12328 for questions-outgoing; Tue, 12 Mar 1996 12:28:50 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA12314 for ; Tue, 12 Mar 1996 12:28:46 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA06344; Tue, 12 Mar 1996 13:25:53 -0700 From: Terry Lambert Message-Id: <199603122025.NAA06344@phaeton.artisoft.com> Subject: Re: network IO profiling To: john@starfire.mn.org Date: Tue, 12 Mar 1996 13:25:53 -0700 (MST) Cc: questions@freebsd.org In-Reply-To: <199603121717.LAA29203@starfire.mn.org> from "john@starfire.mn.org" at Mar 12, 96 11:17:18 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Are there tools to help gauge system network IO performance? iostat, > bonnie, and such don't seem to do any network stuff... > > Please respond directly, as I do not get this list... All of the ones that I am aware of, like ttcp (the test program) tend to neglect latency. The NFS tests, like NFSBench, have the same drawbacks. To get latency measures, you need to install a request/response server of some kind (like Samba) and run something like "LANPerf" or Ziff-Davis' "WinBench" series against it over the wire. What is ultimately useful depends on what you are testing for (as opposed to what you think you are testing for). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.