From owner-freebsd-current Mon Mar 20 10:13:30 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA01663 for current-outgoing; Mon, 20 Mar 1995 10:13:30 -0800 Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA01655 for ; Mon, 20 Mar 1995 10:13:25 -0800 Received: from caramba.cs.tu-berlin.de (wosch@caramba.cs.tu-berlin.de [130.149.18.7]) by mail.cs.tu-berlin.de (8.6.10/8.6.10) with ESMTP id TAA22372; Mon, 20 Mar 1995 19:13:06 +0100 From: Wolfram Schneider Received: (wosch@localhost) by caramba.cs.tu-berlin.de (8.6.10/8.6.9) id TAA16838; Mon, 20 Mar 1995 19:13:00 +0100 Date: Mon, 20 Mar 1995 19:13:00 +0100 Message-Id: <199503201813.TAA16838@caramba.cs.tu-berlin.de> To: "Christoph P. Kukulies" Cc: freebsd-current@freefall.cdrom.com Subject: iozone read vs. write In-Reply-To: <199503201602.RAA02319@gilberto.physik.rwth-aachen.de> References: <199503201602.RAA02319@gilberto.physik.rwth-aachen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: current-owner@FreeBSD.org Precedence: bulk Christoph P. Kukulies writes: > iozone 13 ... > > Writing the 13 Megabyte file, 'iozone.tmp'...15.085938 seconds > Reading the file...4.000000 seconds > > IOZONE performance measurements: > 903589 bytes/second for writing the file > 3407872 bytes/second for reading the file > > Does anone have an explanation why the number diverge to such an extent? > (System is a 32 MB 486DX2/66 EIDE 2 Quantum 540 system) Ja. $ more REAMDE In order for this to be a fair test, the length of the test file must be AT LEAST 2X the amount of disk cache memory for your system. If not, you are really testing the speed at which your CPU can read blocks out of the cache (not a fair test) Wolfram