From owner-freebsd-questions Thu May 9 16:46:23 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA07075 for questions-outgoing; Thu, 9 May 1996 16:46:23 -0700 (PDT) Received: (from jmb@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA07067 Thu, 9 May 1996 16:46:21 -0700 (PDT) From: "Jonathan M. Bresler" Message-Id: <199605092346.QAA07067@freefall.freebsd.org> Subject: Re: Benchmarking To: chuckr@Glue.umd.edu (Chuck Robey) Date: Thu, 9 May 1996 16:46:21 -0700 (PDT) Cc: FreeBSD-Questions@FreeBSD.ORG In-Reply-To: from "Chuck Robey" at May 9, 96 03:53:13 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Chuck Robey wrote: > > I need to compare two motherboards here, so could anyone tell me what I > should do to test CPU/memory ONLY ? I don't want disk access to show up > at all in testing (or if it does, very minimally). > http://www.scl.ameslab.gov/scl/HINT/HINT.html this is an excellent benchmark. the problem data set fits into cache (onchip) initially, then doubles in size till the machine starts to page the process' data space. on many machines, this producees a graph of computaton vs memory footprint. the graph has steps. each step show the size of the on-chip cache, L2 cache, and finally main memory. jmb -- Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG FreeBSD--4.4BSD Unix for PC clones, source included. http://www.freebsd.org/