From owner-freebsd-questions@FreeBSD.ORG Wed Apr 26 09:44:12 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 741C316A473 for ; Wed, 26 Apr 2006 09:44:12 +0000 (UTC) (envelope-from howells@kde.org) Received: from mail.devrandom.org.uk (host-84-9-223-82.bulldogdsl.com [84.9.223.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 686D143D72 for ; Wed, 26 Apr 2006 09:44:07 +0000 (GMT) (envelope-from howells@kde.org) Received: from localhost (localhost [127.0.0.1]) by mail.devrandom.org.uk (Postfix) with ESMTP id 76626FD050 for ; Wed, 26 Apr 2006 10:43:50 +0100 (BST) Received: from mail.devrandom.org.uk ([127.0.0.1]) by localhost (mail.devrandom.org.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 51569-09 for ; Wed, 26 Apr 2006 10:43:44 +0100 (BST) Received: from [192.168.1.175] (unknown [192.168.1.175]) by mail.devrandom.org.uk (Postfix) with ESMTP id C3D15FD04B for ; Wed, 26 Apr 2006 10:43:44 +0100 (BST) Message-ID: <444F40CE.5090400@kde.org> Date: Wed, 26 Apr 2006 10:43:42 +0100 From: Chris Howells User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <20060426031606.33136.qmail@web33302.mail.mud.yahoo.com> In-Reply-To: <20060426031606.33136.qmail@web33302.mail.mud.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at devrandom.org.uk 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 09:44:12 -0000 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=0 ttl=64 time=1.97 ms > 65515 bytes from node: icmp_seq=1 ttl=64 time=1.95 ms > 65515 bytes from node: icmp_seq=2 ttl=64 time=1.94 ms > 65515 bytes from node: icmp_seq=3 ttl=64 time=1.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=0 ttl=128 time=0.844 ms 64 bytes from 10.0.0.5: icmp_seq=1 ttl=128 time=0.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.