From owner-freebsd-hackers Tue Mar 6 7:57:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 13A8537B718 for ; Tue, 6 Mar 2001 07:57:19 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id KAA05629; Tue, 6 Mar 2001 10:57:17 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.2/8.9.1) id f26Fulc19217; Tue, 6 Mar 2001 10:56:47 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15013.2238.953211.516979@grasshopper.cs.duke.edu> Date: Tue, 6 Mar 2001 10:56:46 -0500 (EST) To: Matt Dillon Cc: Subject: Re: Machines are getting too damn fast In-Reply-To: <200103060013.f260DHY46910@earth.backplane.com> References: <200103060013.f260DHY46910@earth.backplane.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt Dillon writes: > > I modified my original C program again, this time to simply read > the data from memory given a block size in kilobytes as an argument. > I had to throw in a little __asm to do it right, but here are my results. > It shows about 3.2 GBytes/sec from the L2 (well, insofar as my > 3-instruction loop goes), and about 1.4 GBytes/sec from main memory. > > > NOTE: cc x.c -O2 -o x > > ./x 4 > 3124.96 MBytes/sec (read) <...> > ./x 1024 > 1397.90 MBytes/sec (read) > > In contrast I get 1052.50 MBytes/sec on the Dell 2400 from the L2, > and 444 MBytes/sec from main memory. > FWIW: 1.2GHz Athlon, VIA Apollo KT133 chipset, Asus A7V motherboard, (PC133 ECC Registered Dimms) ./x 4 2393.70 MBytes/sec (read) ./x 8 2398.19 MBytes/sec (read) <...> ./x 1024 627.32 MBytes/sec (read) And a Dual 933MHz PIII SuperMicro 370DER Serverworks HE-SL Chipset (2-way interleaved PC133 ECC Registered DIMMS) ./x 4 1853.54 MBytes/sec (read) ./x 1024 526.19 MBytes/sec (read) There's something diabolic about your previous bw test, though. I think it only hits one bank of interleaved ram. On the 370DER it gets only 167MB/sec. Every other bw test I've run on the box shows copy perf at around 260MB/sec (Hbench, lmbench). I see the same problem on a PE4400 (also 2-way interleaved); it shows copy perf as 111MB/sec. Every other test has it at 230MB/sec. The Athlon copies at 174MB/sec, which is right about what lmbench, hbench, etc, and your test show. How's your P4 for floating point? Is real-life perf as good as the specbench numbers would indicate, or do you need a better compiler than GCC to get any benefit from it? My wife is a statistician, and she runs some really fp intensive workloads. This Athlon is faster than the Serverworks box and (barely) faster than a year-old Alpha UP1000 for her code. Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message