From owner-freebsd-questions@FreeBSD.ORG Wed Apr 26 12:45:23 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1379C16A401 for ; Wed, 26 Apr 2006 12:45:23 +0000 (UTC) (envelope-from ldrada@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DF4F43D46 for ; Wed, 26 Apr 2006 12:45:22 +0000 (GMT) (envelope-from ldrada@gmail.com) Received: by nproxy.gmail.com with SMTP id m18so1175229nfc for ; Wed, 26 Apr 2006 05:45:21 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=j98w6y+IY9lKLrrE8iZx3JVwpUvIEBZxB3iySuio08CXNF5VXDSQFgpboMXdRB7Cbxcf3HNg6WY5ZLBlpBL97gGqMzI5BMelEKzBbgflu3dZoR2SJuv0WemNwDcCBlN6icasRgHC764YS88Sa1NodKon9cMzYpvh9ga4odF+n18= Received: by 10.48.30.9 with SMTP id d9mr1973240nfd; Wed, 26 Apr 2006 02:59:41 -0700 (PDT) Received: by 10.49.2.5 with HTTP; Wed, 26 Apr 2006 02:59:41 -0700 (PDT) Message-ID: <5ceb5d550604260259y6d663228p5e85518a73f8bc4c@mail.gmail.com> Date: Wed, 26 Apr 2006 11:59:41 +0200 From: "Daniel A." To: "Chris Howells" In-Reply-To: <444F40CE.5090400@kde.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060426031606.33136.qmail@web33302.mail.mud.yahoo.com> <444F40CE.5090400@kde.org> Cc: freebsd-questions@freebsd.org Subject: Re: How to verify speed of a 1Gb/s network? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Apr 2006 12:45:23 -0000 On 4/26/06, Chris Howells wrote: > Rob wrote: > > > How can I verify that a 1Gb/s network is indeed > > operating at its optimal speed? I tried this: > > By transferring large amounts of data using a light-weight protocol > (maybe FTP) and timing the amount of time it takes. > > Also various testing utilities, for instance ttcp. > > > [master]$ ping -s 65507 node > > 65515 bytes from node: icmp_seq=3D0 ttl=3D64 time=3D1.97 ms > > 65515 bytes from node: icmp_seq=3D1 ttl=3D64 time=3D1.95 ms > > 65515 bytes from node: icmp_seq=3D2 ttl=3D64 time=3D1.94 ms > > 65515 bytes from node: icmp_seq=3D3 ttl=3D64 time=3D1.97 ms > > This is a measure of latency only. > > For instance, I can easily get 10ms pings on 512kbit/sec ADSL. It can > only transfer data at ~60 KB/sec though. > > I can get these values on a very lightly loaded 100Mbit/sec network: > > chris@merlin$ ping 10.0.0.5 > PING 10.0.0.5 (10.0.0.5): 56 data bytes > 64 bytes from 10.0.0.5: icmp_seq=3D0 ttl=3D128 time=3D0.844 ms > 64 bytes from 10.0.0.5: icmp_seq=3D1 ttl=3D128 time=3D0.740 ms > > > PS: I verified my calculation method for two > > computers here on a 100Mbit/s network, from which > > I get: > > time with ping: 12.4 ms > > ideal calculated time: 10 ms > > Sounds like your 100Mbit/s network is very heavily loaded, you would > expect ~1ms pings. Please notice that he is transferring 65515 bytes, not 64 (Like you did)