Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264398AbTE0Wnm (ORCPT ); Tue, 27 May 2003 18:43:42 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264403AbTE0Wnm (ORCPT ); Tue, 27 May 2003 18:43:42 -0400 Received: from inet-mail3.oracle.com ([148.87.2.203]:30415 "EHLO inet-mail3.oracle.com") by vger.kernel.org with ESMTP id S264398AbTE0Wnk (ORCPT ); Tue, 27 May 2003 18:43:40 -0400 Date: Tue, 27 May 2003 15:54:32 -0700 From: Joel Becker To: linux-kernel@vger.kernel.org Subject: WimMark I report for 2.5.70 Message-ID: <20030527225432.GK32128@ca-server1.us.oracle.com> Mail-Followup-To: linux-kernel@vger.kernel.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Burt-Line: Trees are cool. X-Red-Smith: Ninety feet between bases is perhaps as close as man has ever come to perfection. User-Agent: Mutt/1.5.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2046 Lines: 47 WimMark I report for 2.5.70 Runs: 1005.78 958.80 947.23 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 runs all do ramp-up work to populate caches and the like. 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. A bigger number is a better number. All things being equal, a delta <50 is close to unimportant, and a delta < 20 is very identical. This benchmark is sensitive to random system events. I run three runs because of this. If two runs are nearly identical and the remaining run is way off, that run should probably be ignored (it is often a low number, signifying that something on the system impacted the benchmark). 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). WimMark I run results are archived at http://oss.oracle.com/~jlbec/wimmark/wimmark_I.html -- "I almost ran over an angel He had a nice big fat cigar. 'In a sense,' he said, 'You're alone here So if you jump, you'd best jump far.'" 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/