Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 19 Mar 2003 18:17:28 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 19 Mar 2003 18:17:27 -0500 Received: from inet-mail2.oracle.com ([148.87.2.202]:4801 "EHLO inet-mail2.oracle.com") by vger.kernel.org with ESMTP id ; Wed, 19 Mar 2003 18:17:26 -0500 Date: Wed, 19 Mar 2003 15:28:13 -0800 From: Joel Becker To: linux-kernel@vger.kernel.org Subject: WimMark I report for 2.5.65-mm2 Message-ID: <20030319232812.GJ2835@ca-server1.us.oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Burt-Line: Trees are cool. User-Agent: Mutt/1.5.3i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1386 Lines: 35 WimMark I report for 2.5.65-mm2 Runs: 1374.22 1487.19 1437.26 WimMark I is a rough benchmark we have been running here at Oracle against various kernels. Each run tests an OLTP workload on the Oracle database with somewhat restrictive memory conditions. This reduces in-memory buffering of data, allowing for more I/O. The I/O is read and sync write, random and seek-laden. The benchmark is called "WimMark I" because it has no official standing and is only a relative benchmark useful for comparing kernel changes. The benchmark is normalized an arbitrary kernel, which scores 1000.0. All other numbers are relative to this. The machine in question is a 4 way 700 MHz Xeon machine with 2GB of RAM. CONFIG_HIGHMEM4GB is selected. The disk accessed for data is a 10K RPM U2W SCSI of similar vintage. The data files are living on an ext3 filesystem. Unless mentioned, all runs are on this machine (variation in hardware would indeed change the benchmark). -- "Senator let's be sincere, As much as you can." Joel Becker Senior Member of Technical Staff Oracle Corporation E-mail: joel.becker@oracle.com Phone: (650) 506-8127 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/